← Home

@voiceflow/semantic-release-config

semantic-release config for voiceflow

2
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

pmvrmcamandasteinhauerandrewlawrencetylerhhaneffervescentiajosh_vfvoiceflow-gallaganz4o4zsssoflyyyxavidopzhilighttrsytolunsanasarjanjughazyanose-voiceflowdandonovan78theprofabuyakninabondarjbydeleyvf-serviceaccountchidi-voiceflowpateriackarjunsehgal-vfrohan-mandhotra-vfmackenzieleudevinabaghmar

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 2 of 2)

Version Deps Published
1.5.0 5 / 0
1.4.3 5 / 0

v1.4.3

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.