@aithos/protocol-core
Aithos protocol — reference implementation of the core primitives (DIDs, ethos, mandates, bundles) used by the CLI and by any host that speaks the protocol.
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@stablelib/xchacha20poly1305 | AI (dependencies): @stablelib/xchacha20poly1305 is a legitimate crypto primitive from the stablelib org; stable dependency for this crypto-focused package. | ai | |
| provenance | no-provenance | AI (provenance): New package from a small org; absence of provenance is common and not a risk signal here. | ai | |
| phantom-deps | phantom-dep:@types/adm-zip | AI (phantom-deps): @types/adm-zip is a type declaration for adm-zip which is a direct runtime dep; phantom detection is a false positive here. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 0.8.0 | 10 / 3 | |
| 0.6.6 | 10 / 3 | |
| 0.6.5 | 10 / 3 | |
| 0.6.4 | 10 / 3 | |
| 0.6.3 | 10 / 3 | |
| 0.6.1 | 10 / 3 | |
| 0.6.0 | 10 / 3 | |
| 0.5.2 | 10 / 3 | |
| 0.5.1 | 10 / 3 | |
| 0.5.0 | 10 / 3 | |
| 0.4.0 | 10 / 3 | |
| 0.3.1 | 10 / 3 | |
| 0.3.0 | 10 / 3 | |
| 0.2.1 | 10 / 3 | |
| 0.2.0 | 10 / 2 | |
| 0.1.2 | 10 / 2 |
v0.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.