@voiceflow/semantic-release-config
semantic-release config for voiceflow
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@semantic-release/npm | AI (phantom-deps): Semantic-release plugins are config-referenced, not directly imported; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@semantic-release/exec | AI (phantom-deps): Semantic-release plugins are config-referenced, not directly imported; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@semantic-release/github | AI (phantom-deps): Semantic-release plugins are config-referenced, not directly imported; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@semantic-release/commit-analyzer | AI (phantom-deps): Semantic-release plugins are config-referenced, not directly imported; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@semantic-release/release-notes-generator | AI (phantom-deps): Semantic-release plugins are config-referenced, not directly imported; stable pattern for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal org config package; no repo URL and tiny payload are expected characteristics, not spam indicators. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 1.6.0 | 5 / 0 | |
| 1.5.0 | 5 / 0 | |
| 1.4.3 | 5 / 0 | |
| 1.4.0 | 5 / 0 | |
| 1.3.0 | 5 / 0 | |
| 1.2.0 | 5 / 13 | |
| 1.1.0 | 5 / 13 | |
| 1.0.9 | 5 / 13 | |
| 1.0.8 | 5 / 13 | |
| 1.0.7 | 5 / 13 | |
| 1.0.6 | 5 / 13 | |
| 1.0.5 | 5 / 13 | |
| 1.0.4 | 5 / 13 | |
| 1.0.3 | 5 / 13 | |
| 1.0.2 | 5 / 13 | |
| 1.0.1 | 5 / 13 | |
| 1.0.0 | 5 / 13 |
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.