@actual-app/sync-server
actual syncing server
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): uuid is a canonical, widely-used package; this addition is benign for this well-established project. | ai | |
| provenance | publisher-changed | AI (provenance): Package publishes via GitHub Actions with SLSA attestation from the official actualbudget org; automation publisher is expected and stable. | ai | |
| dependencies | unvetted-dep:@actual-app/crdt | AI (dependencies): First-party sibling package from the same actualbudget publisher; expected dependency for CRDT-based sync functionality. | ai | |
| dependencies | unvetted-dep:nordigen-node | AI (dependencies): Open-banking API client used for Actual Budget's bank sync feature; legitimate and expected dependency. | ai | |
| provenance | no-provenance | AI (provenance): Actual Budget is an established open-source project; lack of Sigstore provenance is a minor gap, not a security concern for this package. | ai | |
| dependencies | unvetted-dep:migrate | AI (dependencies): Standard database migration library; expected for a server application managing a SQLite database. | ai | |
| dependencies | unvetted-dep:pluggy-sdk | AI (dependencies): Banking API SDK used for Actual Budget's bank sync feature; legitimate and expected dependency. | ai | |
| dependencies | unvetted-dep:@actual-app/web | AI (dependencies): First-party sibling package from the same actualbudget publisher; expected dependency for this sync server. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 26.6.0 | 18 / 16 | |
| 26.5.2 | 17 / 14 | |
| 26.5.1 | 17 / 14 | |
| 26.5.0 | 16 / 14 | |
| 26.4.0 | 19 / 17 |
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.