Its stable release line and organization backing provide useful continuity. Ten runtime dependencies increase upkeep exposure, while the missing license limits safe adoption.
48%
Total Score
50
50
70
50
The package has 49 releases and a roughly 26-day median interval, but no releases in the last 12 months and the latest release was about four years ago. The long historical record helps, but does not offset the current inactivity.
There were no commits and no active maintainers in the last three months, consistent with the package having had no release for about four years. The non-archived repository and organization ownership provide only limited compensation.
Ten runtime dependencies create a relatively broad maintenance and transitive-risk surface for a small package, with no development dependencies shown to provide additional testing context.
No declared license or license file was found in the package or repository, leaving the legal terms for reuse unclear.
The repository has no security policy, reducing transparency for reporting and handling vulnerabilities. This is a hygiene gap rather than evidence of unsafe code by itself.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
infrajs/ans Version ~1 | — | — |
infrajs/doc Version ~1 | — | — |
infrajs/load Version ~1 | — | — |
infrajs/path Version ~1 | — | — |
infrajs/cache Version ~1 | — | — |
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.