A tiny, normalized JavaScript and JSON message envelope for every runtime boundary
87%
Total Score
70
100
95
88
50
No build attestation, trusted publisher, or staged-publishing evidence is present, leaving release origin less independently verifiable despite the package's otherwise transparent source repository.
Only one registry account has publish access, which creates release-continuity risk, although repository activity shows another active contributor.
The repository is owned by an individual account rather than an organization, so the single registry maintainer and concentrated contributor activity provide less organizational continuity.
Two contributors were active in the last 3 months; the leading contributor made 5 of 7 commits, so activity is concentrated but not dependent on one contributor.
No repository security policy was found, reducing clarity about vulnerability reporting and response expectations.
We didn't find any vulnerabilities for this package.
No direct dependencies.
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.