@semantic-release/condition-travis
Check Travis CI environment before publishing
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
Keywords
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 to semantic-release-bot, the official automation account for the semantic-release org. This transition occurred in 2017 and is well-established as legitimate across the entire semantic-release package family. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 7.1.4 | 4 / 13 | |
| 7.1.3 | 4 / 13 | |
| 7.1.2 | 4 / 13 | |
| 7.1.1 | 4 / 13 | |
| 7.1.0 | 4 / 13 | |
| 7.0.1 | 4 / 13 | |
| 7.0.0 | 4 / 13 | |
| 6.2.1 | 5 / 20 | |
| 6.2.0 | 5 / 20 | |
| 6.1.1 | 5 / 20 | |
| 6.1.0 | 5 / 20 | |
| 6.0.3 | 3 / 19 | |
| 6.0.2 | 3 / 19 | |
| 6.0.1 | 3 / 19 | |
| 6.0.0 | 3 / 7 | |
| 5.0.2 | 3 / 7 | |
| 5.0.1 | 3 / 9 | |
| 5.0.0 | 2 / 9 | |
| 4.1.4 | 2 / 8 | |
| 4.1.2 | 1 / 8 | |
| 4.1.0 | 2 / 9 | |
| 4.0.0 | 1 / 7 | |
| 3.0.0 | 1 / 7 | |
| 2.0.0 | 1 / 7 | |
| 1.0.0 | 1 / 7 |
v7.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.0
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.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.0
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.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
2 findingsThis version was published by a different npm account than previous versions on 2017-09-19. 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.
v6.0.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2017-08-19. This could indicate a legitimate maintainer transition or an account compromise.