utility functions for archiver
58%
Total Score
75
88
50
50
The release has no build provenance attestation or staged publishing evidence, so consumers cannot verify how the published artifact was produced. This lowers supply-chain transparency without making the package unfit by itself.
The package has 16 releases since November 2015, but none in roughly 2 years and 6 months; this is a meaningful maintenance warning for a dependency.
The repository recorded zero commits and zero active maintainers in the last 3 months. Its recent push timestamp provides some evidence of repository activity, but not of ongoing development.
The linked repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This is a transparency gap, though it is less serious than the maintenance slowdown.
No type declarations are included, which adds integration friction for TypeScript consumers. This is a consumer-ergonomics gap rather than evidence of abandonment.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
glob Version ^10.0.0 | — | — |
lodash Version ^4.17.15 | — | — |
is-stream Version ^2.0.1 | — | — |
lazystream Version ^1.0.0 | — | — |
graceful-fs Version ^4.2.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.