@actual-app/core
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:handlebars | AI (dependencies): Pre-existing dependency in this package; not newly introduced in this version. | ai | |
| dependencies | unvetted-dep:hyperformula | AI (dependencies): Pre-existing dependency in this package; not newly introduced in this version. | ai | |
| provenance | missing-githead | AI (provenance): Artifact of CI/CD pipeline change; SLSA provenance attestation provides stronger commit linkage. | ai | |
| provenance | publisher-changed | AI (provenance): Shift to GitHub Actions CI publisher is consistent with SLSA attestation; legitimate automation change for this org. | ai | |
| phantom-deps | phantom-dep:@rschedule/json-tools | AI (phantom-deps): @rschedule/json-tools is a legitimate scheduling library dependency used in this budgeting app; phantom detection is a false positive. | ai | |
| phantom-deps | phantom-dep:typescript | AI (phantom-deps): typescript appears in both dependencies and devDependencies in this monorepo package; it's a legitimate build tooling dependency, not a phantom dep indicating malice. | ai | |
| phantom-deps | phantom-dep:@reduxjs/toolkit | AI (phantom-deps): @reduxjs/toolkit is a legitimate state management dependency for the Actual Budget client code; phantom detection is a false positive for this package. | ai | |
| phantom-deps | phantom-dep:typescript-strict-plugin | AI (phantom-deps): typescript-strict-plugin is a legitimate TypeScript tooling dependency; phantom detection is a false positive for this monorepo package. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): @actual-app/core is the legitimate core library for Actual Budget under the @actual-app scoped namespace; 'core' vs 'cors' is a false positive Levenshtein match, not a typosquat. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Metadata hygiene issues (no description, no repo URL) are consistent with an internal library; 41 versions and 5.6k weekly downloads confirm legitimate, established package. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decoding in encryption/app.ts is standard decryption code for a budget app that handles encrypted user data; no exfiltration or malicious payload pattern present. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 26.5.2 | 21 / 30 | |
| 26.5.1 | 21 / 30 | |
| 26.5.0 | 20 / 30 | |
| 26.4.0 | 21 / 33 | |
| 26.3.0 | 22 / 30 |
v26.5.2
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
v26.5.1
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
v26.5.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
This 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
2 findingsPackage name '@actual-app/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v26.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.