@onereach/step-voice
Onereach.ai Voice Steps
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 | no-provenance | AI (provenance): Long-established org package; lack of Sigstore provenance is consistent across all 601 versions and not a risk indicator here. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 7.0.20 | 4 / 23 | |
| 7.0.18 | 4 / 23 | |
| 7.0.16 | 4 / 23 | |
| 7.0.7 | 4 / 23 | |
| 7.0.6 | 4 / 23 | |
| 7.0.5 | 4 / 23 | |
| 7.0.4 | 4 / 23 |
v7.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.