@flowlib/version-control
Version control plugin for Flowlib — sync flows to GitHub/GitLab/Bitbucket as .flow.ts files
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@flowlib/core | AI (dependencies): Sibling package in the same @flowlib monorepo; risk tracks with the monorepo as a whole. | ai | |
| provenance | no-provenance | AI (provenance): New package family without provenance setup; not a security signal on its own. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.0.7 | 5 / 10 | |
| 0.0.6 | 5 / 10 | |
| 0.0.5 | 4 / 10 | |
| 0.0.3 | 3 / 10 | |
| 0.0.1 | 3 / 10 |
v0.0.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.