ES2015-compliant shim for Number.isNaN - the global isNaN returns false positives.
68%
Total Score
75
100
94
70
Two of five workflows use pull_request_target, which warrants care because that trigger can expose elevated automation context. However, no untrusted checkouts or script-injection patterns were detected.
A prepublish lifecycle script is present. This is not evidence of a harmful package by itself, but it adds avoidable publication or installation complexity compared with a package without lifecycle scripts.
The package has existed since January 2014 with nine releases, but its latest registry release was in December 2020 and there were no releases in the last 12 months. The repository's later push provides some compensation, but the published release cadence remains stale.
There were no commits and no active maintainers in the last three months. The recent repository push offsets a full abandonment judgment, but current maintenance activity is still weak.
All five analyzed workflows omit top-level token permissions, so their default access is not explicitly constrained. No workflow declares top-level write access, but the missing restrictions are a meaningful hygiene gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
call-bind Version ^1.0.0 | — | — |
define-properties Version ^1.1.3 | — | — |
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.