brightnucleus/keys
The source is complete and easy to inspect, with tests, a changelog, an MIT license, and no install-time scripts. Despite that transparency, there is no evidence of ongoing maintenance or security process, creating substantial abandonment risk.
38%
Total Score
25
75
75
Health Score Breakdown
The package has had no release in about 9 years; its three releases were concentrated in July 2017. This is strong evidence of abandonment risk, although the repository is not archived.
The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with the long release gap. No newer activity is provided to offset this concern.
Only one registry publishing maintainer is listed, which limits visible publishing continuity. The organization-owned repository provides some backing, so this is a supporting caution rather than a standalone severe risk.
Composer build tooling is present, but no security scanning tools are configured. This is a modest hygiene gap and does not outweigh the maintenance concerns.
The repository has no security policy, reducing transparency about vulnerability reporting and response. This matters more given the absence of recent maintenance evidence.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Alain Schlesser |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 ramsey/uuid Version ^3 | — | — |
brightnucleus/exceptions Version >=0.2 | — | — |
brightnucleus/validation Version >=0.1 | — | — |
Weekly Downloads
Info
- Last Published
- 9 years ago
- Created
- 9 years ago
Are You Affected?
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.
I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.