@smithers-orchestrator/accounts
Manage multiple Claude/Codex/Gemini/Kimi subscription and API-key accounts that Smithers agents can round-robin through.
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): Consistent across all versions of this package; no provenance is common and not a standalone risk signal here. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 0.23.0 | 1 / 2 | |
| 0.22.0 | 1 / 2 | |
| 0.21.0 | 1 / 2 | |
| 0.20.4 | 1 / 2 | |
| 0.20.3 | 1 / 2 | |
| 0.20.1 | 1 / 2 | |
| 0.20.0 | 1 / 2 | |
| 0.19.0 | 1 / 2 | |
| 0.18.0 | 1 / 2 | |
| 0.17.0 | 1 / 2 | |
| 0.16.9 | 1 / 2 |
v0.23.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.