A mirror of Facebook's Warning
60%
Total Score
50
100
88
50
Only one registry account has publish access, which creates a thin publishing base. This is partly consistent with the individually owned repository but still limits resilience if that maintainer becomes unavailable.
The latest release was published in February 2019, more than seven years ago, with no releases in the past 12 months. This is a meaningful freshness concern despite a long package history and stable version.
There were no commits and no active maintainers in the last three months. The repository's October 2024 push provides some compensating evidence, but current maintenance capacity remains uncertain.
The repository reports no build tool or security scanning tool. For this small, directly shipped JavaScript utility this is a modest transparency gap rather than a severe dependency risk.
No security policy was found, reducing the project's documented path for reporting vulnerabilities. The package's small scope limits the practical impact but does not remove the transparency gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
loose-envify 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.