@xyo-network/archivist-memory
2
Versions
—
License
No
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
atrouwjoelbcarterrphansen91jordantrouwjonesmac
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): CI/CD environment change; no security concern for this well-established namespace. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): atrouw is an org account with 288 approved packages; consistent with internal maintainer transition. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): xyo removed as part of same org-level account transition; no evidence of hostile takeover. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): All 4 new deps are @xyo-network scoped at matching version pins; internal package split, not foreign injection. | ai | |
| provenance | publisher-changed | AI (provenance): xyo org account with 450 approved packages; transition from personal to org account is consistent across the monorepo. | ai |
v5.0.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.
v5.0.0
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.