@openclaw/bluebubbles
OpenClaw BlueBubbles 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 | publisher-changed | AI (provenance): Package publishes via GitHub Actions CI/CD with SLSA attestation; automated publisher is expected and stable. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Active development project; maintainer addition alongside CI/CD pipeline setup is a normal team expansion pattern. | ai | |
| semgrep | semgrep:etc-passwd-access | AI (semgrep): Appears in a test asserting the code rejects /etc/passwd paths — security validation, not credential harvesting. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): Raw IPs are private/local addresses used as test fixtures in test files, not production network calls. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 2026.5.7 | 0 / 2 | |
| 2026.5.6 | 0 / 2 | |
| 2026.5.5 | 0 / 2 | |
| 2026.5.4 | 0 / 2 | |
| 2026.5.3 | 0 / 2 | |
| 2026.5.2 | 0 / 2 | |
| 2026.3.13 | 1 / 0 | |
| 2026.3.12 | 1 / 0 | |
| 2026.3.11 | 1 / 0 | |
| 2026.3.10 | 1 / 0 | |
| 2026.3.7 | 1 / 0 | |
| 2026.3.2 | 0 / 0 | |
| 2026.3.1 | 0 / 0 | |
| 2026.2.25 | 0 / 0 | |
| 2026.2.24 | 0 / 0 | |
| 2026.2.23 | 0 / 1 | |
| 2026.2.22 | 0 / 1 | |
| 2026.2.21 | 0 / 1 | |
| 2026.2.19 | 0 / 1 | |
| 2026.2.17 | 0 / 1 | |
| 2026.2.15 | 0 / 1 | |
| 2026.2.14 | 0 / 1 | |
| 2026.2.13 | 0 / 1 |
v2026.5.7
2 findingsThis version was published by a different npm account than previous versions on 2026-05-07. 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.6
2 findingsThis version was published by a different npm account than previous versions on 2026-05-06. 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.5
2 findingsThis version was published by a different npm account than previous versions on 2026-05-06. 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.4
2 findingsThis version was published by a different npm account than previous versions on 2026-05-05. 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.3
2 findingsThis version was published by a different npm account than previous versions on 2026-05-04. 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.2
2 findingsThis version was published by a different npm account than previous versions on 2026-05-02. 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
2 findingsAccessing /etc/passwd or /etc/shadow — credential harvesting on Linux 162 | cfg: createConfig(), 163 | to: "chat:123", > 164 | mediaPath: "/etc/passwd", 165 | }), 166 | ).rejects.toThrow(/mediaLocalRoots/i);
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2026.3.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.3.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.2.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.2.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.2.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.2.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.2.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.2.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.2.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2026.2.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2026.2.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2026.2.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.