← Home

@txo/semantic-release

npm Repository Homepage

Technology Studio - Semantic release

10
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

rostislav-simoniktechnology-studio-ownertxo-agent

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern dormant-publish AI (publish-pattern): No content changes; consistent CI/CD provenance, no takeover indicators. ai
dependencies unvetted-dep:semantic-release-slack-bot AI (dependencies): semantic-release-slack-bot is a known semantic-release plugin; stable false positive for this config package. ai
phantom-deps phantom-dep:semantic-release-slack-bot AI (phantom-deps): Config-wrapper package; deps are re-exported for consumers, not directly imported in source. ai
phantom-deps phantom-dep:@semantic-release/changelog AI (phantom-deps): Config-wrapper package; deps are re-exported for consumers, not directly imported in source. ai
phantom-deps phantom-dep:semantic-release AI (phantom-deps): Config-wrapper package; deps are re-exported for consumers, not directly imported in source. ai
bogus-package bogus-package AI (bogus-package): Config-wrapper packages legitimately have thin READMEs and no keywords; not spam. ai
phantom-deps phantom-dep:conventional-changelog-conventionalcommits AI (phantom-deps): Config-wrapper package; deps are re-exported for consumers, not directly imported in source. ai
phantom-deps phantom-dep:@semantic-release/git AI (phantom-deps): Config-wrapper package; deps are re-exported for consumers, not directly imported in source. ai

Versions (showing 10 of 10)

Version Deps Published
2.0.18 5 / 2
2.0.17 5 / 2
2.0.16 5 / 2
2.0.15 5 / 2
2.0.14 5 / 2
2.0.13 5 / 2
2.0.12 5 / 2
2.0.11 5 / 2
2.0.10 5 / 2
2.0.9 4 / 2

v2.0.18

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.0.17

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.0.16

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.0.14

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.0.12

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.0.10

1 finding
LOW No provenance attestation provenance

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

v2.0.9

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.