@cyia/vscode-valibot-config
VSCode configuration manager based on Valibot schemas
2
Versions
—
License
No
Install Scripts
Verified
Provenance
Supply chain provenance
Status for the latest visible version.
SLSA provenance attestation
npm registry signatures
gitHead linked
Maintainers
wszgrcy
Keywords
vscodeconfigurationvalibotschemaextensionsettingsreactive
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from manual publish (wszgrcy) to GitHub Actions CI/CD with SLSA provenance; author unchanged. | ai |
v1.0.8
2 findings
HIGH
Publisher changed: wszgrcy → GitHub Actions (on 2026-04-28)
provenance
This version was published by a different npm account than previous versions on 2026-04-28. This could indicate a legitimate maintainer transition or an account compromise.
INFO
Has SLSA provenance attestation
provenance
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.7
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.