@cleocode/lafs-protocol
15
Versions
—
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 — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
kryptobaseddev
Keywords
lafsllmagentprotocolschemaconformance
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher changed to GitHub Actions as part of CI/CD automation; SLSA provenance attestation cryptographically ties the artifact to the original maintainer's repo. This pattern is stable for this package. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 1.8.0 | 4 / 8 | |
| 1.7.0 | 4 / 8 | |
| 1.5.0 | 4 / 8 | |
| 1.4.1 | 4 / 8 | |
| 1.4.0 | 4 / 8 | |
| 1.3.2 | 4 / 8 | |
| 1.3.1 | 4 / 8 | |
| 1.2.3 | 4 / 8 | |
| 1.2.2 | 4 / 8 | |
| 1.2.1 | 4 / 8 | |
| 1.2.0 | 4 / 8 | |
| 1.1.0 | 4 / 8 | |
| 1.0.0 | 3 / 8 | |
| 0.1.1 | 2 / 4 | |
| 0.1.0 | 2 / 4 |
v1.8.0
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.
v1.4.1
1 finding
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.2.3
1 finding
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.