The organization-backed repository and stable release note offer limited positive context. The two-file package, decade-long lack of releases, repository name mismatch, and absent security policy leave little evidence of ongoing maintenance or transparency.
42%
Total Score
100
70
50
This is the only release, published over 10 years ago, with no releases in the last 12 months. That is strong evidence of abandonment risk, with no newer release activity to compensate.
The linked repository name does not match the package name, and no README mention was collected. For a two-file package this may reflect a related repository, but ownership of the exact package is less transparent.
The repository has no security policy. This is a transparency gap, although the package is a small static media artifact and the absence is not as serious as it would be for executable code.
We didn't find any vulnerabilities for this package.
No maintainer information available.
No direct dependencies.
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.