There is no security policy or repository scanning, reducing transparency for maintenance and vulnerability response. Tests, a README, a small dependency surface, and no install-time scripts make the artifact easier to inspect and adopt.
38%
Total Score
0
100
71
83
The package has had no release in more than eight years, and its nine-release history shows no releases in the last 12 months. This is strong evidence of abandonment risk.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and leaving little evidence of ongoing maintenance.
The manifest declares MIT, while the artifact license file is detected as MIT-0. Although a license file exists, the mismatch creates avoidable legal uncertainty for dependents.
Composer build tooling is present, but no security scanning tools were detected. This weakens automated vulnerability oversight, especially alongside the absence of recent maintenance.
The repository has no security policy, so consumers have no documented process for reporting or receiving fixes for vulnerabilities.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
sledgehammer/core Version >=18 | — | — |
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 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.