@interfere/sdk
[](https://opensource.org/licenses/MIT)
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 11.0.4 | 1 / 3 | |
| 11.0.3 | 1 / 3 | |
| 11.0.1 | 1 / 3 | |
| 11.0.0 | 1 / 3 | |
| 9.0.3 | 1 / 2 | |
| 9.0.2 | 1 / 3 | |
| 9.0.0 | 1 / 3 | |
| 8.1.6 | 1 / 3 | |
| 8.1.2 | 1 / 6 | |
| 8.1.0 | 1 / 6 | |
| 1.1.2 | 1 / 6 | |
| 1.0.3 | 1 / 6 | |
| 1.0.2 | 1 / 6 | |
| 1.0.1 | 1 / 6 | |
| 1.0.0 | 1 / 6 |
v11.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (skve) than the most recent previously approved version (GitHub Actions) on 2026-07-13, but skve is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v11.0.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (skve) than the most recent previously approved version (GitHub Actions) on 2026-07-10, but skve is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.