steroids/document
The MIT license, small runtime dependency set, and organization-backed repository reduce adoption friction. Its short README and absent security policy provide limited transparency, while the release and maintenance record remain the main concern.
42%
Total Score
50
100
64
75
Health Score Breakdown
The package has had no releases in the last 12 months, with the latest release on January 26, 2022, despite 26 releases over roughly five years. This strongly indicates abandonment risk.
There were zero commits and zero active maintainers in the last three months, consistent with the repository having stopped after January 2022. This is strong evidence of inactive maintenance.
Composer build tooling is present, but no security-scanning tooling was detected. The missing scanning is a modest hygiene gap, not a standalone adoption blocker.
The linked repository is not archived, although its last push was on January 26, 2022. The active archive status is positive, but it does not offset the long inactivity shown by commit and release history.
The repository has no security policy. That weakens vulnerability-reporting transparency, especially for a package with no recent maintenance activity.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 steroids/core Version * | — | — |
Weekly Downloads
Info
- Last Published
- 4 years ago
- Created
- 5 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.