@vibecontrols/vibe-plugin-agent-aiconfig
Cross-harness configuration management via Bridle
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
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 2026.601.1 | 2 / 4 | |
| 2026.529.1 | 2 / 4 | |
| 2026.525.2 | 2 / 4 | |
| 2026.525.1 | 2 / 4 | |
| 2026.518.1 | 2 / 4 | |
| 2026.512.1 | 2 / 4 | |
| 2026.510.1 | 2 / 4 | |
| 2026.509.3 | 2 / 4 | |
| 2026.509.1 | 2 / 4 | |
| 2026.508.2 | 1 / 4 | |
| 2026.428.4 | 1 / 4 |
v2026.601.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.529.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.525.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.525.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.518.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.512.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.510.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.509.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.509.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.508.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.428.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.