88%
Total Score
90
100
94
75
100
One contributor made about 89% of the 81 recent commits, creating concentration risk. The organization-owned project and five additional active contributors partly compensate, so this is a caution rather than a severe abandonment signal.
The repository name does not match the package and its README does not mention it, which creates some package-to-repository identity ambiguity. The package is a utility used by electron-builder, so the mismatch is consistent with a monorepo or subpackage relationship but remains a transparency caution.
No repository security policy was found, leaving vulnerability-reporting expectations and response procedures less transparent.
All nine workflows were analyzed with no high- or medium-severity findings, all 36 action references are pinned, and most workflows use read-only permissions. A high-confidence low-severity adhoc-packages finding shows that one release workflow installs outside a lockfile, so this is a minor hygiene concern.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
js-yaml Version ^4.1.0 | — | — |
fs-extra Version ^10.1.0 | — | — |
builder-util Version 26.15.3 | — | — |
app-builder-lib Version 26.15.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.