Properly escape JSON for usage as an object literal inside of a `` tag
63%
Total Score
50
100
88
75
50
No build attestation or trusted-publisher identity is present, reducing publication transparency. This is a supply-chain hygiene gap rather than evidence that the release is unsafe.
Only one registry account has publish access. That is a limited publishing base and creates resilience concerns if the maintainer becomes unavailable, with no organizational backing shown.
The package has four releases since September 2014, with the latest published in March 2016 and none in the past 12 months. This is a meaningful maintenance concern, though the small, stable scope may reduce the need for frequent releases.
There were zero commits and zero active maintainers in the past three months. The repository's last push was in 2022, so current maintenance capacity appears limited.
The repository uses no build tool and has no detected security-scanning tools. The simple six-file JavaScript package keeps the build gap modest, but security visibility is limited.
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.