The MIT license and package-to-repository match improve transparency. No security policy and a very small project footprint add uncertainty for a package handling API keys.
38%
Total Score
25
70
50
The package has only one release, published about 9 years ago, with no releases in the last 12 months. This strongly suggests abandonment risk despite the absence of registry deprecation.
The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with the last push having occurred about 9 years ago. No provided maintenance signal compensates for this inactivity.
Two issues remain open, while there were no new or closed issues and no pull-request activity in the last month. This is supporting evidence of low ongoing maintenance rather than a severe risk by itself.
The repository has 0 stars and 10 forks, with 3 watchers. The low visible adoption provides little supporting maturity evidence, though popularity is not decisive for a small package.
The linked repository has no security policy. For a package described as managing API keys, this is a meaningful transparency gap, although it does not by itself show a security defect.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/support Version ~5.1 | — | — |
bantenprov/workflow Version 1.0.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.