@openclaw/matrix
OpenClaw Matrix channel plugin
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 | no-provenance | AI (provenance): Provenance is rare on npm; not a disqualifier for this package. | ai | |
| provenance | publisher-changed | AI (provenance): Package publishes via GitHub Actions CI with SLSA attestation; machine publisher is expected and stable. | ai | |
| phantom-deps | phantom-dep:@matrix-org/matrix-sdk-crypto-wasm | AI (phantom-deps): Platform-specific binary dep for matrix-sdk-crypto; not directly imported but required at runtime. | ai | |
| dependencies | unvetted-dep:markdown-it | AI (dependencies): markdown-it is a widely-used, well-maintained Markdown parser; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@vector-im/matrix-bot-sdk | AI (dependencies): Element/Vector-im's official Matrix bot SDK fork; expected dependency for a Matrix channel plugin. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 2026.6.1 | 8 / 0 | |
| 2026.5.28 | 8 / 0 | |
| 2026.5.19 | 8 / 2 | |
| 2026.5.18 | 8 / 2 | |
| 2026.3.13 | 6 / 0 | |
| 2026.3.7 | 6 / 0 |
v2026.6.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2026.5.28
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2026.5.19
2 findingsThis version was published by a different npm account than previous versions on 2026-05-20. 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.
v2026.5.18
2 findingsThis version was published by a different npm account than previous versions on 2026-05-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.
v2026.3.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2026.3.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.