@smithers-orchestrator/memory
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Young monorepo package; lack of provenance is consistent across the @smithers-orchestrator scope and not a standalone risk signal. | ai | |
| phantom-deps | phantom-dep:@smithers-orchestrator/driver | AI (phantom-deps): Same-org monorepo sibling; declared as runtime dep, phantom-dep heuristic misfires on indirect usage patterns. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 0.22.0 | 8 / 2 | |
| 0.21.0 | 8 / 2 | |
| 0.20.4 | 8 / 2 | |
| 0.20.3 | 9 / 2 | |
| 0.20.1 | 9 / 2 | |
| 0.20.0 | 9 / 2 | |
| 0.19.0 | 9 / 2 | |
| 0.18.0 | 9 / 2 | |
| 0.17.0 | 9 / 2 | |
| 0.16.9 | 8 / 2 | |
| 0.16.8 | 8 / 2 | |
| 0.16.7 | 8 / 2 | |
| 0.16.6 | 8 / 2 | |
| 0.16.5 | 8 / 2 | |
| 0.16.4 | 8 / 2 | |
| 0.16.3 | 8 / 2 | |
| 0.16.1 | 8 / 2 | |
| 0.16.0 | 8 / 2 |
v0.22.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.