@changesets/pre
Utils to make a Changesets repo enter and exit pre mode
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Legitimate transition from original maintainer (noviny) to the project's dedicated release bot (changesets-release-bot) in 2020. | ai | |
| provenance | no-provenance | AI (provenance): Published in 2020, before npm Sigstore provenance existed. Not actionable for this package's older versions. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): @babel/runtime is injected by Babel's transform-runtime plugin at build time; correctly declared but not directly imported. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 2.0.2 | 4 / 1 | |
| 2.0.1 | 4 / 1 | |
| 2.0.0 | 5 / 1 | |
| 1.0.14 | 5 / 1 | |
| 1.0.13 | 5 / 1 | |
| 1.0.12 | 5 / 1 | |
| 1.0.11 | 5 / 1 | |
| 1.0.10 | 5 / 1 | |
| 1.0.9 | 5 / 1 | |
| 1.0.8 | 5 / 1 | |
| 1.0.7 | 5 / 1 | |
| 1.0.6 | 5 / 1 | |
| 1.0.5 | 5 / 1 | |
| 1.0.4 | 5 / 1 | |
| 1.0.3 | 5 / 1 | |
| 1.0.2 | 5 / 1 | |
| 1.0.1 | 5 / 1 | |
| 1.0.0 | 5 / 1 | |
| 0.2.0 | 5 / 1 | |
| 0.1.1 | 5 / 1 | |
| 0.1.0 | 5 / 2 |
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
2 findingsThis version was published by a different npm account than previous versions on 2020-03-29. 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.
v1.0.0
2 findingsThis version was published by a different npm account than previous versions on 2020-03-11. 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.