The assert module from Node.js, for the browser.
62%
Total Score
75
100
83
67
50
No build attestation or trusted-publisher provenance is present, leaving publication origin less transparent, but this is a transparency gap rather than evidence of an unsafe release.
A prepare script runs during installation, adding execution during dependency setup and therefore some supply-chain hygiene risk; no evidence here shows that it is harmful.
The package has a long history and 16 releases, but its latest release was about three years ago and it had no releases in the last 12 months, lowering confidence in active maintenance.
There were zero commits and zero active maintainers in the last three months, reinforcing the concern that maintenance has slowed substantially.
The repository uses established build tooling, but it reports no security-scanning tools, leaving automated security hygiene less visible.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
util Version ^0.12.5 | — | — |
is-nan Version ^1.3.2 | — | — |
call-bind Version ^1.0.2 | — | — |
object-is Version ^1.1.5 | — | — |
object.assign Version ^4.1.4 | — | — |
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.