monospice/spicy-identifiers
Risky to adopt: the package has had no release or repository activity since January 2017, suggesting it is effectively abandoned. It remains licensed, documented, and backed by a matching organization repository, but those positives do not offset the lack of maintenance.
42%
Total Score
50
100
64
75
Health Score Breakdown
Only one release exists, published in January 2017, with no releases in the last 12 months. Roughly nine years without a release is a strong abandonment concern for a dependency.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the package having received no meaningful maintenance since January 2017.
Composer build tooling is present, but no security scanning tools are reported. This is a modest hygiene gap rather than the main reason to avoid the release.
The repository is not archived, which avoids an explicit abandonment marker, but its last push was in January 2017 and does not compensate for the prolonged inactivity.
The repository has no security policy. This is a transparency gap, although the small, inactive project and absence of workflow automation limit the practical significance compared with the maintenance risk.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Cy Rossignol |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 monospice/spicy-identifier-tools Version ~1.0 | — | — |
Weekly Downloads
Info
- Last Published
- 9 years ago
- Created
- 9 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.