Documentation, tests, licensing, and security reporting are all in place. The small maintainer base leaves less backup if development stops.
66%
Total Score
50
100
94
88
One contributor made all commits in the last three months, leaving no demonstrated backup maintainer in the recent activity window. The repository owner is an individual rather than an organization, so there is no shown organizational handoff capacity to offset this.
Only one commit was recorded in the last three months, despite a release on 2026-07-30. The recent release is positive, but the limited observed development activity warrants caution.
The assessed release is 4.0.0-beta.1, so it carries pre-release compatibility risk even though pre-releases represent only about 9% of recent releases.
All four workflows were analyzed, but all 12 action references are unpinned, which weakens build reproducibility. The audit also reports a high-confidence bot-conditions issue in the Dependabot auto-merge workflow and a top-level write permission there; the pull_request_target trigger has no untrusted checkout or script-injection sink, so this is a hygiene concern rather than a severe standalone risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
react/promise Version ^3.3 | — | — |
react/event-loop Version ^1.6 | — | — |
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.