← Home

@canonmsg/codex-plugin

npm Repository Homepage

Canon host integration for Codex CLI

51
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

Keywords

canoncodexcoding-agentmessaginghost-mode

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance missing-githead AI (provenance): Absence of gitHead is a minor publish-env change; no corroborating malicious signals across 59 versions of this package. ai
dependencies unvetted-dep:@canonmsg/bridge AI (dependencies): Same @canonmsg namespace/monorepo as the package; consistent with internal refactor, not a third-party injection. ai
provenance no-provenance AI (provenance): Package has no provenance attestation but no other risk signals; acceptable for this package. ai

Versions (showing 51 of 71)

View all versions
Version Deps Published
0.23.3 3 / 3
0.23.2 3 / 3
0.23.1 3 / 3
0.23.0 3 / 3
0.22.4 3 / 3
0.22.3 3 / 3
0.22.2 3 / 3
0.22.1 3 / 3
0.22.0 3 / 3
0.21.0 3 / 3
0.20.0 6 / 3
0.19.2 6 / 3
0.19.1 6 / 3
0.19.0 6 / 3
0.18.12 3 / 3
0.18.11 3 / 3
0.18.10 3 / 3
0.18.9 3 / 3
0.18.8 3 / 3
0.18.7 3 / 3
0.18.6 3 / 3
0.18.5 3 / 3
0.18.4 3 / 3
0.18.3 2 / 3
0.18.2 2 / 3
0.18.1 2 / 3
0.18.0 2 / 3
0.14.1 2 / 3
0.14.0 2 / 3
0.13.3 2 / 3
0.13.2 2 / 3
0.13.1 2 / 3
0.13.0 2 / 3
0.12.0 2 / 3
0.11.12 2 / 3
0.11.11 2 / 3
0.11.10 2 / 3
0.11.9 2 / 3
0.11.8 2 / 3
0.11.7 2 / 3
0.11.6 2 / 3
0.11.5 2 / 3
0.11.4 2 / 3
0.11.3 2 / 3
0.11.2 2 / 3
0.11.1 2 / 3
0.11.0 2 / 3
0.10.0 2 / 3
0.9.8 2 / 3
0.9.7 2 / 3
0.9.6 2 / 3

v0.23.3

1 finding
INFO No provenance attestation provenance

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

v0.23.2

1 finding
INFO No provenance attestation provenance

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

v0.23.1

2 findings
INFO No provenance attestation provenance

[Accepted risk] 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.23.0

2 findings
INFO No provenance attestation provenance

[Accepted risk] 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.22.4

1 finding
INFO No provenance attestation provenance

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

v0.22.3

1 finding
INFO No provenance attestation provenance

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

v0.22.2

1 finding
INFO No provenance attestation provenance

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

v0.22.1

1 finding
INFO No provenance attestation provenance

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

v0.22.0

2 findings
INFO No provenance attestation provenance

[Accepted risk] 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.21.0

2 findings
INFO No provenance attestation provenance

[Accepted risk] 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.20.0

2 findings
INFO No provenance attestation provenance

[Accepted risk] 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.19.2

2 findings
INFO No provenance attestation provenance

[Accepted risk] 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.19.1

1 finding
INFO No provenance attestation provenance

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

v0.19.0

1 finding
INFO No provenance attestation provenance

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

v0.18.12

1 finding
INFO No provenance attestation provenance

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

v0.18.11

1 finding
INFO No provenance attestation provenance

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

v0.18.10

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.

INFO No provenance attestation provenance

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

v0.18.9

1 finding
INFO No provenance attestation provenance

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

v0.18.8

1 finding
INFO No provenance attestation provenance

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

v0.18.7

1 finding
INFO No provenance attestation provenance

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