@agora-protocol/crypto MIT 3 versions

@agora-protocol/crypto

npm Repository Homepage

ACP cryptographic primitives: Ed25519, X25519, ChaCha20-Poly1305, SHA-256

Versions

MIT

License

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

mscarlos107

Keywords

acpagentprotocolai-agentsed25519x25519chacha20-poly1305sha-256

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
typosquat	typosquat.levenshtein:bcrypt	AI (typosquat): Scoped package implementing crypto primitives; Levenshtein match to bcrypt is coincidental, not impersonation.	ai	2026/05/27
phantom-deps	phantom-dep:@agora-protocol/core	AI (phantom-deps): Same org scope; likely used transitively or as a type dependency rather than direct import.	ai	2026/05/27

Versions (showing 3 of 3)

Version	Deps	Published
0.3.3	4 / 2	2026-05-06
0.3.2	4 / 2	2026-05-02
0.3.1	4 / 2	2026-04-29

v0.3.3

1 finding

LOW No provenance attestation provenance

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

v0.3.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.