serve
Static file serving and directory listing
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): vercel-release-bot is Vercel's official release automation account with a strong track record (4140 approved versions). The transition from leerobinson is a legitimate org-level change. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Vercel consolidated npm publishing under vercel-release-bot, removing individual contributor accounts. This is an organizational practice, not a takeover signal. | ai | |
| provenance | missing-githead | AI (provenance): serve is a well-established Vercel package; missing gitHead reflects a publish environment change, not a security concern. Stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Lack of Sigstore provenance is a best-practice gap, not a security risk for this established Vercel package published via vercel-release-bot. | ai |
Versions (showing 100 of 154)
| Version | Deps | Published |
|---|---|---|
| 14.2.6 | 11 / 14 | |
| 14.2.5 | 11 / 14 | |
| 14.2.4 | 11 / 13 | |
| 14.2.3 | 11 / 13 | |
| 14.2.2 | 11 / 13 | |
| 14.2.1 | 11 / 13 | |
| 14.2.0 | 11 / 13 | |
| 14.1.2 | 11 / 13 | |
| 14.1.1 | 11 / 13 | |
| 14.1.0 | 12 / 12 | |
| 14.0.1 | 11 / 10 | |
| 14.0.0 | 10 / 10 | |
| 13.0.4 | 9 / 0 | |
| 13.0.3 | 9 / 3 | |
| 13.0.2 | 9 / 3 | |
| 13.0.1 | 9 / 3 | |
| 13.0.0 | 9 / 3 | |
| 12.0.1 | 9 / 3 | |
| 12.0.0 | 9 / 3 | |
| 11.3.2 | 9 / 3 | |
| 11.3.1 | 9 / 3 | |
| 11.3.0 | 9 / 3 | |
| 11.2.0 | 9 / 3 | |
| 11.1.0 | 9 / 3 | |
| 11.0.2 | 9 / 3 | |
| 11.0.1 | 9 / 3 | |
| 11.0.0 | 9 / 3 | |
| 10.1.2 | 9 / 3 | |
| 10.1.1 | 9 / 3 | |
| 10.1.0 | 9 / 3 | |
| 10.0.2 | 8 / 3 | |
| 10.0.1 | 8 / 3 | |
| 10.0.0 | 8 / 3 | |
| 9.6.0 | 8 / 3 | |
| 9.4.2 | 8 / 3 | |
| 9.4.1 | 8 / 3 | |
| 9.4.0 | 8 / 3 | |
| 9.3.0 | 8 / 3 | |
| 9.2.0 | 8 / 3 | |
| 9.1.2 | 8 / 3 | |
| 9.1.1 | 8 / 3 | |
| 9.1.0 | 8 / 3 | |
| 9.0.0 | 8 / 3 | |
| 8.2.0 | 6 / 3 | |
| 8.1.4 | 6 / 3 | |
| 8.1.3 | 6 / 3 | |
| 8.1.2 | 6 / 3 | |
| 8.1.1 | 6 / 3 | |
| 8.1.0 | 6 / 3 | |
| 8.0.0 | 6 / 3 | |
| 7.2.0 | 6 / 3 | |
| 7.1.6 | 6 / 3 | |
| 7.1.5 | 6 / 3 | |
| 7.1.4 | 6 / 3 | |
| 7.1.3 | 6 / 3 | |
| 7.1.2 | 6 / 3 | |
| 7.1.1 | 6 / 3 | |
| 7.1.0 | 6 / 3 | |
| 7.0.1 | 6 / 3 | |
| 7.0.0 | 9 / 3 | |
| 6.5.8 | 22 / 7 | |
| 6.5.7 | 23 / 7 | |
| 6.5.6 | 22 / 7 | |
| 6.5.5 | 22 / 9 | |
| 6.5.4 | 22 / 9 | |
| 6.5.3 | 22 / 9 | |
| 6.5.2 | 22 / 9 | |
| 6.5.1 | 22 / 7 | |
| 6.5.0 | 22 / 7 | |
| 6.4.11 | 22 / 7 | |
| 6.4.10 | 22 / 7 | |
| 6.4.9 | 22 / 7 | |
| 6.4.8 | 21 / 7 | |
| 6.4.7 | 21 / 7 | |
| 6.4.6 | 21 / 7 | |
| 6.4.5 | 21 / 7 | |
| 6.4.4 | 21 / 7 | |
| 6.4.3 | 21 / 7 | |
| 6.4.2 | 21 / 7 | |
| 6.4.1 | 21 / 7 | |
| 6.4.0 | 21 / 7 | |
| 6.3.1 | 21 / 7 | |
| 6.3.0 | 21 / 7 | |
| 6.2.0 | 20 / 5 | |
| 6.1.0 | 20 / 5 | |
| 6.0.6 | 20 / 5 | |
| 6.0.5 | 20 / 5 | |
| 6.0.4 | 20 / 5 | |
| 6.0.3 | 20 / 5 | |
| 6.0.2 | 20 / 5 | |
| 6.0.1 | 20 / 5 | |
| 6.0.0 | 20 / 5 | |
| 5.2.4 | 20 / 5 | |
| 5.2.3 | 20 / 5 | |
| 5.2.2 | 20 / 5 | |
| 5.2.1 | 20 / 5 | |
| 5.2.0 | 20 / 5 | |
| 5.1.5 | 19 / 5 | |
| 5.1.4 | 19 / 5 | |
| 5.1.3 | 19 / 5 |
v14.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.2.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: vercel-release-bot.
v14.2.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: vercel-release-bot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.1.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: vercel-release-bot.
v14.1.1
3 findingsThis version was published by a different npm account than previous versions on 2022-11-08. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: vercel-release-bot.
v14.1.0
3 findingsThis version was published by a different npm account than previous versions on 2022-11-08. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: vercel-release-bot.
v14.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.3
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-07-06. This could indicate a legitimate maintainer transition or an account compromise.
v13.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2021-11-04. This could indicate a legitimate maintainer transition or an account compromise.