82%
Total Score
healthy
Frequent releases and active organization backing outweigh a workflow token-permission concern and weak direct package-to-repository naming.
The repository name does not match the package and its README does not mention the package, which is a caution because the linkage is less explicit; the organization-owned monorepo context partly explains the mismatch.
No repository security policy was found, leaving vulnerability-reporting guidance less transparent than it could be.
All 11 workflows were analyzed, with no untrusted checkouts, script injection, or unpinned action references. However, three high-confidence findings report blanket GitHub App token permissions in the v2 publish workflow, creating a meaningful release-workflow hygiene concern.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
idb Version 8.0.0 | — | — |
tslib Version ^2.4.1 | — | — |
@amplitude/targeting Version 0.3.11 | — | — |
@amplitude/rrweb-types Version 2.0.0-alpha.40 | — | — |
@amplitude/rrweb-record Version 2.0.0-alpha.40 | — | — |
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.