← Home

serve

npm Repository Homepage

Static file serving and directory listing

51
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

rauchgtimneutkensvercel-release-botzeit-botleoarunoda

Keywords

vercelservemicrohttp-server

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 51 of 154)

Show 1 prerelease View all versions
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

v14.2.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v14.2.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v14.2.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v14.2.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v14.2.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v14.2.1

2 findings
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Missing gitHead — previous versions had it provenance

[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 findings
HIGH Missing gitHead — previous versions had it provenance

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.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v14.1.2

2 findings
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Missing gitHead — previous versions had it provenance

[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 findings
HIGH Publisher changed: leerobinson → vercel-release-bot (on 2022-11-08) provenance

This 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.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Missing gitHead — previous versions had it provenance

[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 findings
HIGH Publisher changed: leerobinson → vercel-release-bot (on 2022-11-08) provenance

This 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.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Missing gitHead — previous versions had it provenance

[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
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v14.0.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v13.0.4

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v13.0.3

2 findings
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: leo → leerobinson (on 2022-07-06) provenance

[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
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v13.0.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v13.0.0

2 findings
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: leerobinson → leo (on 2021-11-04) provenance

[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.