82%
Total Score
healthy
Active, well-backed project with strong maintenance signals, but workflow findings and package-to-repository linkage gaps add caution.
No build attestation is present, so consumers have less independently verifiable publication provenance; the trusted publisher identity provides some compensating context but not an attestation.
The repository name does not match the package and its README does not mention the package, so the linkage is less transparent; the monorepo context makes a name mismatch ordinary, but the missing mention remains a caution.
No type declarations are included, which reduces ergonomics for TypeScript consumers, but this is a consumer-experience gap rather than evidence of abandonment or unsafe maintenance.
All 24 workflows were analyzed, but one file failed; 75 of 156 action references are unpinned, and high-confidence template-injection findings plus adhoc package installs remain hygiene concerns. No untrusted checkout or script-injection sink was reported, so these findings do not independently establish a severe workflow risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
ts-morph Version 12.0.0 | — | — |
@vercel/static-config Version 3.4.4 | — | — |
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.