78%
Total Score
healthy
Active releases and broad project backing outweigh missing types, absent package README, and workflow hygiene concerns.
No build attestation is available, so the release has less publication transparency than an attested build. The trusted publisher identity provides some compensating context but does not replace an attestation.
The linked repository name does not match the package and its README does not mention @vercel/hydrogen. Although monorepo subpackages can legitimately use a shared repository, this leaves package-to-source ownership less transparent.
No type declarations are included. This creates integration friction for consumers, although the small compiled artifact limits the scope of the gap.
All 24 workflows were analyzed, with no untrusted checkouts or script-injection findings. However, 75 of 156 action references are unpinned, one file failed analysis, and the audit reports high-confidence template-injection findings plus ad hoc package installation; these are workflow hygiene concerns, not evidence that the package itself is unsafe.
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.