zoopcommerce/havok
The MIT license, tests, changelog, and matching repository make the project easier to inspect. A single registry maintainer is less concerning because the repository is organization-owned, but no security policy reduces transparency.
38%
Total Score
50
75
50
Health Score Breakdown
The latest release was published in October 2013, nearly 13 years before collection, with no releases in the last 12 months. This is strong evidence of abandonment despite the package having four historical releases.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with a project whose development has effectively stopped.
Composer is used for builds, but no security scanning tools were detected. The missing scanner is a hygiene gap rather than evidence that the release is unsafe by itself.
The repository has no security policy, leaving vulnerability-reporting expectations and security contacts unclear. This is a transparency gap, although it is secondary to the lack of maintenance.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Tim Roediger |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 dojo/dojo Version ~1.9 | — | — |
dojo/util Version ~1.9 | — | — |
dojo/dijit Version ~1.9 | — | — |
zoopcommerce/pixie Version * | — | — |
zoopcommerce/mystique-js Version ~1.2 | — | — |
Weekly Downloads
Info
- Last Published
- 12 years ago
- Created
- 13 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.