Get the byte length of an ArrayBuffer, even in engines without a `.byteLength` method.
68%
Total Score
83
100
94
75
50
No build attestation or trusted-publisher setup was observed, reducing publication transparency. This is a supply-chain hygiene gap rather than evidence that the release is unsafe.
The package declares prepack and prepublish lifecycle scripts. These can add build-time complexity, but the available packaging and repository structure provide context rather than evidence of an unsafe install hook.
The package has only 3 releases and none in the last 12 months; the latest release was about 21 months ago. This is a meaningful maintenance concern for a dependency, though the package may be stable and small.
The repository had 0 commits and 0 active maintainers in the last 3 months, indicating currently quiet maintenance and increasing abandonment risk.
All 6 workflows were analyzed with no reported audit findings, and 5 use read-only permissions. However, all 6 action references are unpinned, leaving a reproducibility and action-substitution hygiene gap; the pull_request_target triggers had no untrusted checkouts or script injection.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
call-bound Version ^1.0.3 | — | — |
is-array-buffer Version ^3.0.5 | — | — |
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.