@openclaw/zalo
OpenClaw Zalo 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 |
|---|---|---|---|---|
| semgrep | semgrep:etc-passwd-access | AI (semgrep): Appears in api.test.ts as a test fixture for malicious input validation, not runtime credential harvesting. | ai | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Standard lazy-loading Proxy pattern using Reflect.get; not obfuscation. | ai | |
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions publisher is intentional CI/CD automation, confirmed by SLSA provenance attestation. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): vincentkoc addition aligns with active project development; no malicious indicators present. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): Raw IP is 127.0.0.1 in a test file; standard localhost test server pattern, not a real network exfiltration risk. | ai |
Versions (showing 39 of 39)
| Version | Deps | Published |
|---|---|---|
| 2026.6.1 | 1 / 0 | |
| 2026.5.28 | 1 / 0 | |
| 2026.5.27 | 1 / 0 | |
| 2026.5.26 | 1 / 0 | |
| 2026.5.22 | 1 / 0 | |
| 2026.5.20 | 1 / 2 | |
| 2026.5.19 | 1 / 2 | |
| 2026.5.18 | 1 / 2 | |
| 2026.5.12 | 1 / 2 | |
| 2026.5.7 | 1 / 2 | |
| 2026.5.6 | 1 / 2 | |
| 2026.5.5 | 1 / 2 | |
| 2026.5.4 | 1 / 2 | |
| 2026.5.3 | 1 / 2 | |
| 2026.5.2 | 1 / 2 | |
| 2026.3.13 | 2 / 0 | |
| 2026.3.12 | 2 / 0 | |
| 2026.3.11 | 2 / 0 | |
| 2026.3.10 | 2 / 0 | |
| 2026.3.7 | 2 / 0 | |
| 2026.3.2 | 1 / 0 | |
| 2026.3.1 | 1 / 0 | |
| 2026.2.25 | 1 / 0 | |
| 2026.2.24 | 1 / 0 | |
| 2026.2.23 | 1 / 1 | |
| 2026.2.22 | 1 / 1 | |
| 2026.2.21 | 1 / 1 | |
| 2026.2.19 | 1 / 1 | |
| 2026.2.17 | 1 / 1 | |
| 2026.2.15 | 1 / 1 | |
| 2026.2.14 | 1 / 1 | |
| 2026.2.13 | 1 / 1 | |
| 2026.2.12 | 1 / 1 | |
| 2026.2.9 | 1 / 1 | |
| 2026.2.6 | 2 / 1 | |
| 2026.2.3 | 2 / 1 | |
| 2026.2.2 | 2 / 1 | |
| 2026.2.1 | 2 / 1 | |
| 2026.1.29 | 2 / 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.27
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2026.5.26
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2026.5.22
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2026.5.20
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
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2026.5.18
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2026.5.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
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
3 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.
Accessing /etc/passwd or /etc/shadow — credential harvesting on Linux Source: https://github.com/openclaw/openclaw/blob/8842a5bd43a6874c86645d00dab80611a94d5850/src/api.test.ts#L122 120 | { 121 | chat_id: "chat-123", > 122 | photo: "file:///etc/passwd", 123 | }, 124 | fetcher,
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.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. Consider requesting the maintainer enable provenance via CI/CD.
v2026.2.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.2.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.2.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.2.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.1.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.