← Home

@canonmsg/core

npm Repository Homepage

Canon core — shared types, REST client, SSE stream, and registration for Canon messaging

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

Keywords

canonmessagingai-agentssserest-client

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern new-deps-added AI (publish-pattern): New dep is a same-org sibling package (@canonmsg/backend-contracts); not a suspicious third-party addition. ai
provenance no-provenance AI (provenance): Low-signal metadata finding; no other risk indicators present for this package. ai
typosquat typosquat.levenshtein:cors AI (typosquat): Scoped @canonmsg/core is a messaging library, not a typosquat of cors; name similarity is coincidental. ai

Versions (showing 74 of 74)

Version Deps Published
8.0.0 1 / 3
7.1.0 1 / 3
7.0.2 1 / 3
5.0.0 1 / 3
4.3.0 1 / 3
4.2.3 1 / 3
4.2.2 1 / 3
4.2.1 1 / 3
3.1.1 1 / 3
3.1.0 1 / 3
3.0.0 1 / 3
2.9.2 1 / 3
2.9.1 1 / 3
2.9.0 1 / 3
2.8.1 1 / 3
2.8.0 1 / 3
2.7.1 1 / 3
2.7.0 1 / 3
2.6.2 1 / 3
2.6.1 1 / 3
2.5.0 1 / 3
2.1.4 0 / 3
2.1.3 0 / 3
2.1.2 0 / 3
2.1.1 0 / 3
2.1.0 0 / 3
2.0.0 0 / 3
1.7.0 0 / 3
1.6.0 0 / 3
1.5.0 0 / 3
1.4.0 0 / 3
1.3.1 0 / 3
1.3.0 0 / 3
1.2.0 0 / 3
1.1.0 0 / 3
1.0.0 0 / 3
0.24.0 0 / 3
0.23.0 0 / 3
0.22.0 0 / 2
0.21.0 0 / 2
0.20.1 0 / 2
0.20.0 0 / 2
0.19.3 0 / 2
0.19.2 0 / 2
0.19.1 0 / 2
0.19.0 0 / 2
0.18.1 0 / 2
0.18.0 0 / 2
0.17.2 0 / 2
0.17.1 0 / 2
0.16.0 0 / 2
0.15.5 0 / 2
0.15.4 0 / 2
0.15.3 0 / 2
0.15.2 0 / 2
0.15.1 0 / 2
0.15.0 0 / 2
0.14.0 0 / 2
0.13.0 0 / 2
0.12.0 0 / 2
0.11.0 0 / 2
0.10.0 0 / 2
0.8.0 0 / 2
0.7.5 0 / 2
0.7.4 0 / 2
0.7.3 0 / 2
0.7.2 0 / 2
0.7.1 0 / 2
0.7.0 0 / 2
0.6.0 0 / 2
0.5.0 0 / 2
0.4.0 0 / 2
0.3.0 0 / 2
0.2.2 0 / 2

v8.0.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.

v7.1.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.

v7.0.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.

v5.0.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.

v4.3.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.

v4.2.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.

v4.2.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.

v4.2.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.

v3.1.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.

v3.1.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.

v3.0.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.

v2.9.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.