79%
Total Score
healthy
Active releases and strong organization backing offset workflow hygiene concerns and a weak package-to-repository match.
The release has no attestation and does not use staged publishing, leaving build origin less independently verifiable than it could be. A trusted publisher identity is present, which partly offsets the gap.
The repository had 24 new issues and 24 new pull requests in the last month, but only four issues closed and no pull requests merged. The active commit and contributor signals provide stronger evidence of ongoing work.
The repository name does not match the package name and its README does not mention the package, so the package-to-repository relationship is not clearly established. The mismatch may reflect a monorepo, but the absent README mention remains a transparency concern.
Version 0.1.82 is not a stable-major release, but it is not a prerelease and recent releases contain no prerelease versions. The main limitation is API maturity implied by the 0.x version.
The audit found no untrusted checkouts or script-injection sinks, but 75 of 156 action references are unpinned, one workflow could not be fully audited, and trusted publishing was flagged. High-confidence template-injection and ad-hoc-package findings are workflow hygiene concerns, while the repository's organization backing and active maintenance provide context rather than eliminating them.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
@vercel/backends Version 19.0.2 | — | — |
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.