@changesets/apply-release-plan
Takes a release plan and applies it to packages
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 |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require is used to load prettier from the consumer's cwd — a standard optional peer dep pattern. Stable and legitimate for this package. | ai | |
| phantom-deps | phantom-dep:outdent | AI (phantom-deps): outdent is a declared runtime dep used in template strings; phantom-dep false positive for this package. | ai |
Versions (showing 51 of 57)
| Version | Deps | Published |
|---|---|---|
| 7.1.1 | 13 / 2 | |
| 7.1.0 | 13 / 2 | |
| 7.0.14 | 13 / 2 | |
| 7.0.13 | 13 / 2 | |
| 7.0.12 | 13 / 2 | |
| 7.0.11 | 13 / 2 | |
| 7.0.10 | 13 / 2 | |
| 7.0.9 | 13 / 2 | |
| 7.0.8 | 13 / 2 | |
| 7.0.7 | 13 / 2 | |
| 7.0.6 | 13 / 2 | |
| 7.0.5 | 13 / 2 | |
| 7.0.4 | 14 / 2 | |
| 7.0.3 | 14 / 2 | |
| 7.0.2 | 14 / 2 | |
| 7.0.1 | 13 / 2 | |
| 7.0.0 | 13 / 2 | |
| 6.1.4 | 13 / 2 | |
| 6.1.3 | 13 / 2 | |
| 6.1.2 | 13 / 3 | |
| 6.1.1 | 13 / 3 | |
| 6.1.0 | 13 / 3 | |
| 6.0.4 | 13 / 3 | |
| 6.0.3 | 13 / 3 | |
| 6.0.2 | 13 / 3 | |
| 6.0.1 | 13 / 3 | |
| 6.0.0 | 13 / 3 | |
| 5.0.5 | 13 / 3 | |
| 5.0.4 | 13 / 2 | |
| 5.0.3 | 13 / 2 | |
| 5.0.2 | 13 / 2 | |
| 5.0.1 | 13 / 2 | |
| 5.0.0 | 13 / 2 | |
| 4.2.0 | 13 / 2 | |
| 4.1.0 | 13 / 2 | |
| 4.0.0 | 12 / 2 | |
| 3.1.0 | 12 / 2 | |
| 3.0.3 | 12 / 2 | |
| 3.0.2 | 12 / 2 | |
| 3.0.1 | 12 / 2 | |
| 3.0.0 | 12 / 2 | |
| 2.0.2 | 12 / 2 | |
| 2.0.1 | 12 / 2 | |
| 2.0.0 | 12 / 2 | |
| 1.0.1 | 12 / 2 | |
| 1.0.0 | 12 / 2 | |
| 0.4.2 | 12 / 2 | |
| 0.4.1 | 12 / 2 | |
| 0.4.0 | 12 / 2 | |
| 0.3.1 | 12 / 2 | |
| 0.3.0 | 12 / 2 |
v7.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
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.