@zeit/schemas — Greenflagged

All schemas used for validation that are shared between our projects

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

matheussnick.traceyvercel-release-botzeit-botmatt.straka

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Publisher change from leo to arunoda occurred in 2018 and is a historical, stable fact. Arunoda is a highly trusted publisher (8788 approved packages). Not a recurring risk signal for this package.	ai	2026/04/24

Versions (showing 61 of 61)

Version	Deps	Published
2.38.0	0 / 5	2025-01-10
2.37.0	0 / 5	2024-09-16
2.36.0	0 / 5	2024-04-25
2.35.0	0 / 5	2024-01-02
2.34.0	0 / 5	2023-12-20
2.33.0	0 / 5	2023-12-19
2.32.0	0 / 5	2023-08-25
2.31.0	0 / 5	2023-04-26
2.30.0	0 / 5	2023-04-20
2.29.0	0 / 5	2023-01-25
2.28.0	0 / 5	2022-09-21
2.27.0	0 / 5	2022-09-21
2.26.0	0 / 5	2022-08-02
2.25.0	0 / 5	2022-08-02
2.24.0	0 / 5	2022-07-12
2.23.0	0 / 5	2022-07-11
2.22.0	0 / 5	2022-07-11
2.21.0	0 / 5	2022-06-28
2.20.0	0 / 5	2022-04-21
2.19.0	0 / 5	2021-10-21
2.18.0	0 / 5	2020-12-14
2.17.0	0 / 5	2020-10-21
2.16.0	0 / 5	2020-07-15
2.15.2	0 / 5	2019-09-30
2.15.1	0 / 5	2019-03-14
2.15.0	0 / 5	2019-03-14
2.14.0	0 / 5	2019-01-09
2.13.0	0 / 5	2018-12-03
2.12.0	0 / 5	2018-11-29
2.11.0	0 / 5	2018-11-15
2.10.0	0 / 5	2018-11-10
2.9.0	0 / 5	2018-11-08
2.8.0	0 / 5	2018-09-19
2.7.0	0 / 5	2018-09-12
2.6.0	0 / 5	2018-09-12
2.5.0	0 / 5	2018-09-12
2.4.0	0 / 5	2018-09-11
2.3.0	0 / 5	2018-08-24
2.2.0	0 / 5	2018-08-22
2.1.1	0 / 5	2018-08-10
2.1.0	0 / 5	2018-08-06
2.0.3	0 / 5	2018-08-02
2.0.2	0 / 5	2018-07-31
2.0.1	0 / 5	2018-07-30
2.0.0	0 / 5	2018-07-30
1.7.0	0 / 5	2018-07-20
1.6.3	0 / 5	2018-07-11
1.6.2	0 / 5	2018-07-08
1.6.1	0 / 5	2018-07-08
1.6.0	0 / 5	2018-07-04
1.5.1	0 / 5	2018-06-29
1.5.0	0 / 5	2018-06-26
1.4.0	0 / 5	2018-06-20
1.3.0	0 / 5	2018-06-19
1.2.0	0 / 5	2018-06-06
1.1.2	0 / 5	2018-05-29
1.1.1	0 / 5	2018-05-28
1.1.0	0 / 5	2018-05-25
1.0.2	0 / 3	2018-05-16
1.0.1	0 / 3	2018-05-16
1.0.0	0 / 3	2018-05-16

v2.38.0

1 finding

LOW No provenance attestation provenance

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

v2.37.0

1 finding

LOW No provenance attestation provenance

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

v2.36.0

1 finding

LOW No provenance attestation provenance

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

v2.35.0

1 finding

LOW No provenance attestation provenance

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

v2.34.0

1 finding

LOW No provenance attestation provenance

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

v2.33.0

1 finding

LOW No provenance attestation provenance

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

v2.32.0

1 finding

LOW No provenance attestation provenance

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

v2.31.0

1 finding

LOW No provenance attestation provenance

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

v2.30.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: gdborton → vercel-release-bot (on 2023-04-20) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2023-04-20. This could indicate a legitimate maintainer transition or an account compromise.

v2.29.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: gdborton → vercel-release-bot (on 2023-01-25) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2023-01-25. This could indicate a legitimate maintainer transition or an account compromise.

v2.28.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: nwienert → gdborton (on 2022-09-21) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2022-09-21. This could indicate a legitimate maintainer transition or an account compromise.

v2.27.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: nwienert → gdborton (on 2022-09-21) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2022-09-21. This could indicate a legitimate maintainer transition or an account compromise.

v2.26.0

1 finding

LOW No provenance attestation provenance

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

v2.25.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: samuel.foster → nwienert (on 2022-08-02) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2022-08-02. This could indicate a legitimate maintainer transition or an account compromise.

v2.24.0

1 finding

LOW No provenance attestation provenance

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

v2.23.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: ernestd → samuel.foster (on 2022-07-11) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2022-07-11. This could indicate a legitimate maintainer transition or an account compromise.

v2.22.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: tknickman → ernestd (on 2022-07-11) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2022-07-11. This could indicate a legitimate maintainer transition or an account compromise.

v2.21.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: tknickman → samuel.foster (on 2022-06-28) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2022-06-28. This could indicate a legitimate maintainer transition or an account compromise.

v2.20.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: anatrajkovska → tknickman (on 2022-04-21) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2022-04-21. This could indicate a legitimate maintainer transition or an account compromise.

v2.19.0

1 finding

LOW No provenance attestation provenance

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

v2.18.0

1 finding

LOW No provenance attestation provenance

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

v2.17.0

1 finding

LOW No provenance attestation provenance

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

v2.16.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: andybitz → anatrajkovska (on 2020-07-15) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2020-07-15. This could indicate a legitimate maintainer transition or an account compromise.

v2.15.2

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: arunoda → andybitz (on 2019-09-30) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2019-09-30. This could indicate a legitimate maintainer transition or an account compromise.

v2.15.1

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: arunoda → andybitz (on 2019-03-14) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2019-03-14. This could indicate a legitimate maintainer transition or an account compromise.

v2.15.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: arunoda → andybitz (on 2019-03-14) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2019-03-14. This could indicate a legitimate maintainer transition or an account compromise.

v2.14.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: javivelasco → arunoda (on 2019-01-09) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2019-01-09. This could indicate a legitimate maintainer transition or an account compromise.

v2.13.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: fivepointseven → javivelasco (on 2018-12-03) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2018-12-03. This could indicate a legitimate maintainer transition or an account compromise.

v2.12.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: tootallnate → fivepointseven (on 2018-11-29) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2018-11-29. This could indicate a legitimate maintainer transition or an account compromise.

v2.11.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: arunoda → tootallnate (on 2018-11-15) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2018-11-15. This could indicate a legitimate maintainer transition or an account compromise.

v2.10.0

1 finding

LOW No provenance attestation provenance

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

v2.9.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: tootallnate → arunoda (on 2018-11-08) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2018-11-08. This could indicate a legitimate maintainer transition or an account compromise.

v2.8.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: arunoda → tootallnate (on 2018-09-19) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2018-09-19. This could indicate a legitimate maintainer transition or an account compromise.

v2.7.0

2 findings

HIGH Publisher changed: leo → arunoda (on 2018-09-12) provenance

This version was published by a different npm account than previous versions on 2018-09-12. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v2.6.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: arunoda → leo (on 2018-09-12) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2018-09-12. This could indicate a legitimate maintainer transition or an account compromise.

v2.5.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: matheuss → arunoda (on 2018-09-12) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2018-09-12. This could indicate a legitimate maintainer transition or an account compromise.

v2.4.0

1 finding

LOW No provenance attestation provenance

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

v2.3.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: tootallnate → matheuss (on 2018-08-24) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2018-08-24. This could indicate a legitimate maintainer transition or an account compromise.

v2.2.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: tootallnate → arunoda (on 2018-08-22) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2018-08-22. This could indicate a legitimate maintainer transition or an account compromise.

v2.1.1

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: tootallnate → pranaygp (on 2018-08-10) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2018-08-10. This could indicate a legitimate maintainer transition or an account compromise.

v2.1.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: tootallnate → arunoda (on 2018-08-06) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2018-08-06. This could indicate a legitimate maintainer transition or an account compromise.

v2.0.3

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: leo → tootallnate (on 2018-08-02) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2018-08-02. This could indicate a legitimate maintainer transition or an account compromise.

v2.0.2

1 finding

LOW No provenance attestation provenance

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

v2.0.1

1 finding

LOW No provenance attestation provenance

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

v2.0.0

1 finding

LOW No provenance attestation provenance

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

v1.7.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: tootallnate → leo (on 2018-07-20) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2018-07-20. This could indicate a legitimate maintainer transition or an account compromise.

v1.6.3

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: tootallnate → pranaygp (on 2018-07-11) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2018-07-11. This could indicate a legitimate maintainer transition or an account compromise.

v1.6.2

1 finding

LOW No provenance attestation provenance

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

v1.6.1

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: leo → tootallnate (on 2018-07-08) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2018-07-08. This could indicate a legitimate maintainer transition or an account compromise.

v1.6.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: arunoda → leo (on 2018-07-04) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2018-07-04. This could indicate a legitimate maintainer transition or an account compromise.

v1.5.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.5.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.4.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.1.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.1.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.