@paperclipai/adapter-opencode-local
Supply chain provenance
Status for the latest visible version.
Maintainers
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 from manual (dotta) to GitHub Actions CI/CD, corroborated by SLSA provenance attestation. This is a legitimate automation migration for this package. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Established package with 32.8k weekly downloads and 224 versions; missing description is a cosmetic metadata issue, not a security signal. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 2026.529.0 | 2 / 2 | |
| 2026.525.0 | 2 / 2 | |
| 2026.517.0 | 2 / 2 | |
| 2026.513.0 | 2 / 2 | |
| 2026.512.0 | 2 / 2 | |
| 2026.428.0 | 2 / 2 | |
| 2026.427.0 | 2 / 2 | |
| 2026.416.0 | 2 / 2 | |
| 2026.403.0 | 2 / 2 | |
| 2026.325.0 | 2 / 2 | |
| 2026.318.0 | 2 / 2 | |
| 0.3.1 | 2 / 2 | |
| 0.3.0 | 2 / 2 |
v2026.529.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2026.525.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2026.517.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2026.513.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2026.512.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2026.427.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2026.416.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2026.403.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2026.325.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2026.318.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-18. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.