Its MIT licensing, focused dependency set, README, and repository tests make adoption straightforward. The small project has no security policy and its sole workflow uses an unpinned action, so maintenance and automation transparency are limited.
57%
Total Score
67
100
88
75
One registry maintainer is a thin publishing base, but the repository and package ownership are aligned with that individual project rather than showing an unexplained organization mismatch.
The package has made no release in nearly five years, with five releases all concentrated on November 8, 2021. This is substantial evidence of inactivity, though a small stable polyfill may need few changes.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with nearly five years without a new release. This increases the risk that issues or compatibility needs will go unattended.
The project uses Composer build tooling, but no security-scanning tool was detected. For this small package that is a transparency gap rather than a severe dependency risk.
No repository security policy was found, leaving vulnerability reporting and response expectations undocumented.
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.