@actual-app/cli
CLI for Actual Budget
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Package is published via GitHub Actions CI/CD with SLSA provenance; automated publisher is expected for this org. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @actual-app/cli is clearly part of the Actual Budget project namespace; Levenshtein distance to 'joi' is a false positive with no plausible confusion. | ai | |
| phantom-deps | phantom-dep:commander | AI (phantom-deps): CLI tool uses Vite bundling; dependencies are bundled at build time and won't appear as direct imports in source analysis. | ai | |
| phantom-deps | phantom-dep:cli-table3 | AI (phantom-deps): CLI tool uses Vite bundling; dependencies are bundled at build time and won't appear as direct imports in source analysis. | ai | |
| phantom-deps | phantom-dep:cosmiconfig | AI (phantom-deps): CLI tool uses Vite bundling; dependencies are bundled at build time and won't appear as direct imports in source analysis. | ai | |
| phantom-deps | phantom-dep:@actual-app/api | AI (phantom-deps): Same-org sibling package bundled via Vite; phantom-dep detection is a false positive for this build pattern. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 26.6.0 | 5 / 6 | |
| 26.5.2 | 4 / 5 | |
| 26.5.1 | 4 / 5 | |
| 26.5.0 | 4 / 5 | |
| 26.4.0 | 4 / 5 |
v26.6.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v26.5.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v26.5.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v26.5.0
2 findingsThis version was published by a different npm account than previous versions on 2026-05-03. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v26.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.