plumphp/plum-date
Tests, documentation, licensing, and a small dependency footprint make the package easy to inspect. The missing security policy leaves limited documented guidance for handling vulnerabilities.
45%
Total Score
100
100
58
83
Health Score Breakdown
The package has only one release, published in October 2015, with no releases in the last 12 months. That long period without a new release is strong evidence of abandonment risk.
The repository is not formally archived, but it was last pushed in October 2015. This compensates for the archive flag itself while still showing that source maintenance has effectively stopped.
The repository has no security policy, so there is no documented process for reporting or handling vulnerabilities. This is a transparency gap, though it is less severe than the prolonged inactivity.
The latest version is v0.1 and is not a stable major release, leaving the public API less mature. Its GitHub release notes document the initial release but do not offset the package's age.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Florian Eckerstorfer |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 plumphp/plum Version ~0.4 | — | — |
Weekly Downloads
Info
- Last Published
- 10 years ago
- Created
- 10 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.