The source repository has no tests, security policy, or recent activity, reducing confidence that defects and vulnerabilities will be addressed. MIT licensing and organization ownership provide useful transparency, but the tiny, inactive project remains a poor long-term dependency choice.
38%
Total Score
50
100
71
75
The latest release was published in May 2016, with no releases in the past 12 months. This long period without a release is strong evidence of abandonment risk.
The repository recorded zero commits and zero active maintainers in the past 3 months, consistent with the release history showing no activity since 2016.
The artifact has no README, tests, or changelog, and the repository also reports no tests or changelog. Missing tests are a meaningful maintenance gap for a library, while the absent artifact changelog is normal packaging practice.
The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, but these counters provide no external sign of active use or community support.
The repository has no security policy, so there is no documented process for reporting or handling vulnerabilities. This adds a transparency gap on top of the project's inactivity.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
asgard/asgard Version ~0.3.0 | — | — |
imagine/imagine Version ~0.3.0 | — | — |
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.