@anolilab/semantic-release-preset
Semantic-release predefined presets.
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Package uses provenance:true and GitHub Actions CI publishing; publisher change from human to GHA is the intended automated release pattern. | ai | |
| phantom-deps | phantom-dep:@semantic-release/exec | AI (phantom-deps): Semantic-release preset; plugins are loaded by the framework at runtime, not imported directly. | ai | |
| phantom-deps | phantom-dep:@semantic-release/github | AI (phantom-deps): Semantic-release preset; plugins are loaded by the framework at runtime, not imported directly. | ai | |
| phantom-deps | phantom-dep:@semantic-release/changelog | AI (phantom-deps): Semantic-release preset; plugins are loaded by the framework at runtime, not imported directly. | ai | |
| phantom-deps | phantom-dep:@semantic-release/git | AI (phantom-deps): Semantic-release preset; plugins are loaded by the framework at runtime, not imported directly. | ai | |
| phantom-deps | phantom-dep:@semantic-release/release-notes-generator | AI (phantom-deps): Semantic-release preset; plugins are loaded by the framework at runtime, not imported directly. | ai | |
| phantom-deps | phantom-dep:conventional-changelog-conventionalcommits | AI (phantom-deps): Semantic-release preset; plugins are loaded by the framework at runtime, not imported directly. | ai | |
| phantom-deps | phantom-dep:@anolilab/semantic-release-clean-package-json | AI (phantom-deps): Same-org plugin loaded at runtime by semantic-release, not directly imported. | ai | |
| phantom-deps | phantom-dep:@semantic-release/commit-analyzer | AI (phantom-deps): Semantic-release preset; plugins are loaded by the framework at runtime, not imported directly. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 13.4.16 | 8 / 0 | |
| 13.4.15 | 8 / 0 | |
| 13.4.14 | 8 / 0 | |
| 13.4.13 | 8 / 0 | |
| 13.4.12 | 8 / 0 | |
| 13.4.11 | 8 / 0 | |
| 13.4.10 | 8 / 0 | |
| 13.4.9 | 8 / 0 | |
| 13.4.8 | 8 / 0 | |
| 13.4.7 | 8 / 0 | |
| 13.4.6 | 8 / 0 | |
| 13.4.5 | 8 / 0 | |
| 13.4.4 | 8 / 0 | |
| 13.4.3 | 8 / 0 | |
| 13.4.2 | 8 / 0 | |
| 13.4.1 | 8 / 0 | |
| 13.4.0 | 8 / 0 | |
| 13.3.0 | 8 / 0 | |
| 13.2.0 | 8 / 0 | |
| 13.1.1 | 8 / 0 | |
| 13.1.0 | 8 / 0 | |
| 13.0.0 | 8 / 0 | |
| 12.1.2 | 8 / 0 | |
| 12.1.1 | 8 / 0 | |
| 12.1.0 | 8 / 0 | |
| 12.0.1 | 8 / 0 | |
| 12.0.0 | 8 / 0 | |
| 11.0.5 | 8 / 0 |
v13.4.16
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v13.4.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v13.4.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v13.4.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v13.4.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v13.4.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v13.4.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v13.4.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v13.4.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v13.4.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v13.4.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v13.4.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v13.4.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v13.4.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v13.4.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v13.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v13.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v13.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v13.1.1
2 findingsThis version was published by a different npm account than previous versions on 2026-02-02. 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.
v13.1.0
2 findingsThis version was published by a different npm account than previous versions on 2026-01-13. 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.
v13.0.0
2 findingsThis version was published by a different npm account than previous versions on 2026-01-08. 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.
v12.1.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v12.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v12.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v12.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v12.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.0.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.