Skip to content

Standard

SLSA

SLSA (Supply-chain Levels for Software Artifacts) is a framework of security standards and provenance attestations for verifying software build integrity.

Known aliases

  • SLSA Build Level 3
  • slsa.dev/provenance/v1
  • SLSA L3
  • SLSA Level 3
  • SLSA provenance
  • Supply-chain Levels for Software Artifacts

Current stories

buildOne report1 publisher

A static denylist stopped one more prompt injection than no protection in a coding-agent study

Bouras, Dai and Mechtaev found a static denylist let 46 of 75 prompt injections execute in a coding agent, against 3 under preflight-scoped capabilities. A same-day Google report of malware stealing OIDC tokens from GitHub Actions runners puts the outer limit on an agent in the CI job's permissions.

Publishers:dev.to

Reality

Evidence45
Adoption
Not scored
Hype gap+10
Incentives
Not scored
Confidence50
securityOne report1 publisher

Chainguard discloses 14 Java bugs that were fixed upstream but never got a CVE

Chainguard disclosed 14 Java vulnerabilities that were fixed upstream but never assigned a CVE, one rated critical and one high. Teams still on the affected versions got no scanner alert, some for years, because nobody announced the fixes when they landed at HEAD.

Publishers:chainguard.dev

Reality

Evidence40
Adoption25
Hype gap+10
Incentives75
Confidence45
securityConfirmed4 publishers

TRACE goes to the Linux Foundation, and the audit question becomes: show me the artifact

The Linux Foundation is taking over an open spec for hardware-signed agent runtime evidence. The producing side now has code and a spec; nobody has yet named who accepts the record.

Perspective Coverage

4 publishers
Builder
Builder 39%
Operator
Operator 46%
Investor
Investor 15%

Reality

Evidence55
Adoption20
Hype gap+30
Incentives70
Confidence60
buildOne report1 publisher

Signed payload's subject binds soit's image to a digest, not directly to its v1.0.0 tag

Reading soit-ai/soit v1.0.0 out of ghcr.io by hand shows how far a container signature reaches. It covers one digest, and the release tag survives as a string in the build predicate that nothing compares for you.

Publishers:dev.to

Reality

Evidence62
Adoption20
Hype gap+25
Incentives55
Confidence60
buildOne report1 publisher

The Mini Shai-Hulud worm passed provenance checks by running inside the release pipeline

Akamai says the May 11-12 wave poisoned a CI cache and minted publish credentials from inside a trusted build, so the attestation it produced was honest. Any gate that only checks for provenance would have passed it.

Publishers:dev.to

Reality

Evidence38
Adoption33
Hype gap+9
Incentives74
Confidence44
buildOne report1 publisher

A comment-triggered Actions workflow published ten malicious npm versions with valid provenance

Socket says all ten bad tarballs of @7nohe/openapi-react-query-codegen carry genuine GitHub Actions attestations, which is what you get when the attestation covers where a build ran rather than who wrote the commit it built.

Publishers:socket.dev

Reality

Evidence66
Adoption58
Hype gap+10
Incentives72
Confidence57
buildOne report1 publisher

OPAQUE gives away the agent audit receipt and sells the machine that prints it

The Linux Foundation now hosts TRACE, a format for evidence of what an AI agent actually did. The package that produces those records still ships as a developer preview.

Publishers:runtimewire.com

Reality

Evidence54
Adoption19
Hype gap+28
Incentives79
Confidence56
productOne report1 publisher

MinIO went dark on 13 February. Docker will keep patching it until 2031, for a fee.

Archiving a project with a billion Docker pulls turned an object store into an audit finding. Docker's extended support does not remove the migration, it moves the deadline out to 2031.

Publishers:docker.com

Reality

Evidence28
Adoption24
Hype gap+34
Incentives92
Confidence32
buildOne report1 publisher

An eBPF egress filter for GitHub Actions that ships with no backend and states what it won't do

field-cage blocks outbound connections from Linux runners in the kernel, keeps its logs on the box, and disclaims step correlation, tamper detection and organization-wide visibility.

Publishers:dev.to

Reality

Evidence34
Adoption9
Hype gap−12
Incentives46
Confidence36
productOne report1 publisher

Docker pipes every agent policy decision into your SIEM, and the evidence burden lands on platform teams

Docker AI Governance now streams every agent policy decision into the SIEM security already runs, with a searchable copy in Docker Cloud. Enforcement was the easy half.

Publishers:docker.com

Reality

Evidence30
Adoption34
Hype gap+38
Incentives86
Confidence55
buildOne report1 publisher

Goish ports Go 1.25's runtime into no_std Rust to test what the concurrency model is worth alone

A one-person project translates Go's scheduler, channels, net/http and crypto/tls into Rust with no GC, no glibc and no Tokio, and stamps every function with its Go source line.

Publishers:dev.to

Reality

Evidence30
Adoption6
Hype gap+38
Incentives68
Confidence42