@vercel/queue
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| module-system | module-system:dual | AI (module-system): Dual CJS/ESM is standard for this package. | ai | |
| provenance | publisher-changed | AI (provenance): Vercel org migrating from vercel-release-bot to GitHub Actions; consistent with CI modernization. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): matheuss and matt.straka are known Vercel employees; legitimate roster update. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removed maintainers are former Vercel staff; normal org churn. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.3.0 | 4 / 8 | |
| 0.2.1 | 4 / 8 | |
| 0.2.0 | 4 / 8 | |
| 0.1.7 | 4 / 8 | |
| 0.1.6 | 4 / 8 | |
| 0.1.5 | 4 / 8 | |
| 0.1.4 | 4 / 8 | |
| 0.1.3 | 4 / 8 | |
| 0.1.2 | 3 / 8 | |
| 0.1.1 | 2 / 7 | |
| 0.1.0 | 2 / 7 | |
| 0.0.2 | 2 / 7 | |
| 0.0.1 | 2 / 7 |
v0.3.0
2 findingsThis version was published by a different npm account than previous versions on 2026-06-04. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
2 findingsThis version was published by a different npm account than previous versions on 2026-06-04. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
2 findingsThis version was published by a different npm account than previous versions on 2026-05-18. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.7
2 findingsThis version was published by a different npm account than previous versions on 2026-05-13. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.