forthend/authority-control
It has a one-person publishing base and no security policy or repository security scanning, limiting ongoing oversight. The MIT declaration, README, changelog, and matching source repository provide useful transparency, but the project appears lightly supported.
38%
Total Score
50
83
83
Health Score Breakdown
Only one registry maintainer is listed, leaving little publishing redundancy; the linked repository is owned by the same individual, so there is no broader organizational backing shown.
The latest release was about 8 years ago, with no releases in the last 12 months; this is strong evidence of abandonment risk despite five historical releases.
The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with the long release gap and indicating no current maintenance.
The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these figures provide no meaningful external adoption signal.
Composer build tooling is present, but no security scanning tooling was detected. This is a modest hygiene gap rather than evidence that the release is unsafe.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 yuantianying |
Direct Dependencies
No direct dependencies.
Weekly Downloads
Info
- Last Published
- 8 years ago
- Created
- 8 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.