← Home

@canonmsg/openclaw-plugin

npm

Canon channel plugin for OpenClaw — messaging with AI agents

74
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

canonmsg

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance missing-githead AI (provenance): No other risk signals; missing gitHead alone is insufficient to reject a package with 61 versions and clean diffs. ai
dependencies unvetted-dep:@canonmsg/bridge AI (dependencies): First-party @canonmsg org dep; consistent with package's ecosystem. ai
dependencies unvetted-dep:@canonmsg/framework AI (dependencies): First-party @canonmsg org dep; consistent with package's ecosystem. ai

Versions (showing 74 of 74)

Version Deps Published
0.18.4 2 / 3
0.18.3 2 / 3
0.18.2 2 / 3
0.18.1 2 / 3
0.18.0 2 / 3
0.17.3 2 / 3
0.17.2 2 / 3
0.17.1 2 / 3
0.17.0 2 / 3
0.16.0 2 / 3
0.15.0 5 / 3
0.14.2 5 / 3
0.14.1 5 / 3
0.14.0 5 / 3
0.13.5 2 / 3
0.13.4 2 / 3
0.13.3 2 / 3
0.13.2 2 / 3
0.13.1 2 / 3
0.13.0 2 / 3
0.12.2 2 / 3
0.11.20 2 / 3
0.11.19 2 / 3
0.11.18 2 / 3
0.11.17 2 / 3
0.11.16 2 / 3
0.11.15 2 / 3
0.11.14 2 / 3
0.11.13 2 / 3
0.11.12 2 / 3
0.11.11 2 / 2
0.11.10 2 / 2
0.11.9 2 / 2
0.11.8 2 / 2
0.11.7 2 / 2
0.11.6 2 / 2
0.11.5 2 / 2
0.11.4 2 / 2
0.11.3 2 / 2
0.11.2 2 / 2
0.11.1 2 / 2
0.11.0 2 / 2
0.10.3 2 / 2
0.10.2 2 / 2
0.10.1 2 / 2
0.9.0 2 / 2
0.8.16 2 / 2
0.8.15 2 / 2
0.8.14 2 / 2
0.8.13 2 / 2
0.8.12 2 / 2
0.8.11 2 / 2
0.8.10 2 / 2
0.8.9 2 / 2
0.8.8 2 / 2
0.8.7 2 / 2
0.8.6 2 / 2
0.8.5 2 / 2
0.8.4 2 / 2
0.8.3 2 / 2
0.8.2 2 / 2
0.8.0 2 / 2
0.7.5 2 / 2
0.7.4 2 / 2
0.7.3 2 / 2
0.7.2 2 / 2
0.7.1 2 / 2
0.7.0 2 / 2
0.6.0 1 / 2
0.5.0 1 / 2
0.4.0 1 / 2
0.3.0 1 / 2
0.2.0 1 / 2
0.1.3 2 / 1

v0.18.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.18.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.18.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.18.1

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: canonmsg.

v0.18.0

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: canonmsg.

v0.17.3

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: canonmsg.

v0.17.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.17.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.17.0

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: canonmsg.

v0.16.0

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: canonmsg.

v0.15.0

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: canonmsg.

v0.14.2

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: canonmsg.

v0.14.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.14.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.13.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.13.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.4

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: canonmsg.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.