A better forEach
68%
Total Score
67
100
83
75
50
No build attestation, trusted publisher, or staged publishing evidence is present. That reduces release transparency, despite the package having a matching source repository.
A prepack lifecycle script is present. This is limited to packaging rather than installation, but it adds build-time behavior that consumers should account for when verifying publication.
The repository is owned by an individual account rather than an organization. That is not inherently unhealthy, but it indicates a thinner formal backing context for a package already showing low recent activity.
The package is mature at 5102 days old, but only six releases have been published and none arrived in the last 12 months. The latest release was about 19 months ago, indicating limited ongoing release activity.
There were no commits and no active maintainers in the last three months. Together with the sparse release history, this is evidence of limited current maintenance.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
is-callable Version ^1.2.7 | — | — |
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.