84%
Total Score
healthy
Frequent releases and signed provenance outweigh workflow permission and package-identification concerns.
The repository name differs from the package and its README does not mention the package, so package ownership is less transparent; the organization-owned monorepo context partly explains the name mismatch but not the missing README reference.
The repository has no SECURITY.md policy, leaving vulnerability-reporting guidance undocumented; this is a transparency gap but not evidence of abandonment.
All 11 workflows were analyzed with no untrusted checkouts, script injection, or unpinned actions. However, three high-confidence findings report blanket GitHub App token permissions in the v2 publishing workflow, creating a real 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.