icanboogie/accessor
The project has a small footprint and no recent commit or release activity, while its single maintainer and absent security policy reduce resilience. Its repository is active enough to remain unarchived, with tests, a clear license, and no install-time scripts.
62%
Total Score
67
83
75
Health Score Breakdown
Only one registry publishing maintainer is listed. Because the source repository is organization-owned, this is normal publishing hygiene but still leaves limited visible release capacity.
The latest release was about three years ago, with no releases in the last 12 months and a median interval of about 10 months. This indicates slow maintenance for a library, without proving abandonment by itself.
The repository recorded no commits and no active maintainers in the last three months. That weakens evidence of ongoing maintenance, although the repository was pushed more recently than the latest registry release.
The repository uses Composer and Make, but no security scanning tools were detected. This is a modest transparency and maintenance gap rather than a severe risk.
No security policy was found in the repository. That makes vulnerability reporting less transparent, though the package still has tests and a documented license.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Olivier Laviale |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 icanboogie/common Version ^1.3.2|^2.0|^6.0 | — | — |
Weekly Downloads
Info
- Last Published
- 3 years ago
- Created
- 11 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.