@changesets/assemble-release-plan
Reads changesets and adds information on dependents that need bumping
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher changed from changesets-release-bot to GitHub Actions as part of a migration to SLSA-attested CI/CD publishing. This is a legitimate and more secure release pipeline for the official changesets project. | ai |
Versions (showing 47 of 47)
| Version | Deps | Published |
|---|---|---|
| 6.0.10 | 6 / 1 | |
| 6.0.9 | 6 / 1 | |
| 6.0.8 | 6 / 1 | |
| 6.0.7 | 6 / 1 | |
| 6.0.6 | 6 / 1 | |
| 6.0.5 | 6 / 1 | |
| 6.0.4 | 6 / 1 | |
| 6.0.3 | 7 / 1 | |
| 6.0.2 | 7 / 1 | |
| 6.0.1 | 7 / 1 | |
| 6.0.0 | 6 / 1 | |
| 5.2.4 | 6 / 1 | |
| 5.2.3 | 6 / 1 | |
| 5.2.2 | 6 / 1 | |
| 5.2.1 | 6 / 1 | |
| 5.2.0 | 6 / 1 | |
| 5.1.3 | 6 / 1 | |
| 5.1.2 | 6 / 1 | |
| 5.1.1 | 6 / 1 | |
| 5.1.0 | 6 / 1 | |
| 5.0.5 | 6 / 1 | |
| 5.0.4 | 6 / 1 | |
| 5.0.3 | 6 / 1 | |
| 5.0.2 | 6 / 1 | |
| 5.0.1 | 6 / 1 | |
| 5.0.0 | 6 / 1 | |
| 4.1.1 | 6 / 1 | |
| 4.1.0 | 6 / 1 | |
| 4.0.1 | 6 / 1 | |
| 4.0.0 | 6 / 1 | |
| 3.0.1 | 6 / 1 | |
| 3.0.0 | 6 / 1 | |
| 2.1.0 | 6 / 1 | |
| 2.0.4 | 6 / 1 | |
| 2.0.3 | 6 / 1 | |
| 2.0.2 | 6 / 1 | |
| 2.0.1 | 6 / 1 | |
| 2.0.0 | 6 / 1 | |
| 1.0.1 | 6 / 1 | |
| 1.0.0 | 6 / 1 | |
| 0.3.1 | 4 / 1 | |
| 0.3.0 | 4 / 1 | |
| 0.2.1 | 3 / 1 | |
| 0.2.0 | 3 / 1 | |
| 0.1.2 | 3 / 1 | |
| 0.1.0 | 3 / 1 | |
| 7.0.0-next.1 | 6 / 1 |
v6.0.10
2 findingsThis version was published by a different npm account than previous versions on 2026-04-17. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.