axstrad/filesystem
Tests, licensing, and a clean package tree provide a useful baseline. The project has had no releases since 2014, no recent commits, and no security scanning, so maintenance risk is substantial.
40%
Total Score
25
69
83
Health Score Breakdown
The package has only three releases, all from December 2014, with none in the last 12 months. This long period without a release is strong evidence of abandonment risk.
There were no commits and no active maintainers in the last three months. Combined with the old last push and release history, this materially increases abandonment risk.
The repository is owned by an individual rather than an organization, so the single registry maintainer does not have organizational backing to compensate for the lack of recent activity.
The repository has zero stars and forks and only two watchers. Popularity is supporting evidence rather than a verdict, but these numbers provide no external adoption signal to offset the stale maintenance record.
Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap rather than a severe risk on its own.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Dan Kempster |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 axstrad/common Version 0.1.* | — | — |
symfony/filesystem Version ~2.0 | — | — |
doctrine/collections Version 1.0.* | — | — |
Weekly Downloads
Info
- Last Published
- 11 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.