jaybizzle/hasmeta
Clear documentation, tests, and an MIT license make the small package straightforward to inspect. Its source has had no commits for about 11 years, with no releases in that period and no security policy, so ownership and compatibility risk are high.
43%
Total Score
0
100
75
75
Health Score Breakdown
The package has had no releases in about 11 years: its latest release was published in October 2014, with zero releases in the last 12 months. This is the strongest evidence of abandonment risk.
The repository recorded zero commits and zero active maintainers during the last three months, consistent with the long release gap and indicating no observable ongoing maintenance.
Composer build tooling is present, but no security scanning tools were detected. That weakens ongoing assurance, though it is secondary to the pronounced maintenance gap.
The repository has no security policy, leaving no documented channel or process for reporting and handling vulnerabilities. This is a transparency gap for a package used in application code.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Mark Beech |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 illuminate/support Version 4.2.*|5.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.