@synnaxlabs/drift
State synchronization and Redux state synchronization for Tauri Apps
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/state-yfMrLzJG.cjs | AI (source-diff): Vite build artifact; minified but fully readable Redux/Zod bundle with no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/state-BFBdNgbN.cjs | AI (source-diff): Standard Vite minified bundle output; code sample shows readable zod/redux-toolkit source, not malicious obfuscation. | ai | |
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI/CD publishing with SLSA attestation; legitimate automation migration for synnaxlabs org. | ai | |
| source-diff | obfuscated-file:dist/state-BGByXBtX.cjs | AI (source-diff): Minified Vite/Rollup chunk output; sample shows standard Redux/toolkit code, not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:dist/state-BghdRGsQ.cjs | AI (source-diff): Standard Vite/Rollup minified bundle output; sample shows readable library code (Redux, Zod), not obfuscation. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): react-dom is a declared peer/runtime dep for this React+Tauri library; phantom-dep heuristic is a false positive here. | ai | |
| phantom-deps | phantom-dep:async-mutex | AI (phantom-deps): async-mutex is a declared runtime dep for this state-sync library; phantom-dep heuristic is a false positive here. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 0.55.0 | 8 / 17 | |
| 0.54.0 | 8 / 17 | |
| 0.52.3 | 9 / 15 | |
| 0.50.0 | 9 / 14 | |
| 0.48.0 | 9 / 13 | |
| 0.47.0 | 9 / 14 | |
| 0.44.0 | 9 / 13 | |
| 0.43.0 | 9 / 13 | |
| 0.42.3 | 9 / 13 | |
| 0.42.1 | 9 / 13 | |
| 0.42.0 | 9 / 13 |
v0.55.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.52.3
3 findingsThis version was published by a different npm account than previous versions on 2026-03-03. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.50.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.48.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.47.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.44.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.43.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.42.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.42.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.42.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.