← Home

@windyroad/voice-tone

Voice and tone enforcement for user-facing copy

4
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

tompahoward

Keywords

claude-codeclaude-code-pluginai-agentai-coding

Versions (showing 4 of 4)

Version Deps Published
0.6.7 0 / 0
0.3.1 0 / 0
0.2.0 0 / 0
0.1.1 0 / 0

v0.6.7

1 finding
HIGH Provenance attestation missing — previous versions had it provenance

[Reject — re-review on republish] (prior reject: AI (provenance): Provenance regression is a strong supply-chain compromise signal; applies until attestation is restored.) This version was published without provenance, but prior versions were published via CI/CD with attestations. This is a strong signal of a potential account compromise or unauthorized publish. The axios attack (March 2026) exhibited exactly this pattern.