@live-change/db-server
Database with observable data for live queries
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:os-service | AI (dependencies): os-service is a well-known native service wrapper; legitimate use in a db-server binary. | ai | |
| phantom-deps | phantom-dep:@live-change/db-store-lmdb | AI (phantom-deps): Same org scope; likely conditionally imported at runtime rather than statically. | ai | |
| phantom-deps | phantom-dep:@live-change/db-store-rbtree | AI (phantom-deps): Same org scope; likely conditionally imported at runtime rather than statically. | ai | |
| phantom-deps | phantom-dep:@live-change/dao-message | AI (phantom-deps): Same-org monorepo dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:line-reader | AI (phantom-deps): Referenced in config files; heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@live-change/db-admin | AI (phantom-deps): Same-org monorepo dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@tailwindcss/vite | AI (phantom-deps): Build/config usage; heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:node-interval-tree | AI (phantom-deps): Referenced in config files; heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@live-change/db-client | AI (phantom-deps): Same-org monorepo dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@live-change/dao-sockjs | AI (phantom-deps): Same-org monorepo dep; stable false positive for this package. | ai |
Versions (showing 22 of 122)
| Version | Deps | Published |
|---|---|---|
| 0.9.104 | 20 / 5 | |
| 0.9.103 | 20 / 5 | |
| 0.9.102 | 20 / 5 | |
| 0.9.101 | 20 / 2 | |
| 0.9.100 | 20 / 2 | |
| 0.9.99 | 20 / 2 | |
| 0.9.98 | 20 / 2 | |
| 0.9.97 | 20 / 2 | |
| 0.9.96 | 20 / 2 | |
| 0.9.95 | 20 / 2 | |
| 0.9.94 | 21 / 2 | |
| 0.9.92 | 21 / 2 | |
| 0.9.89 | 21 / 2 | |
| 0.9.88 | 21 / 2 | |
| 0.9.87 | 21 / 2 | |
| 0.9.86 | 21 / 2 | |
| 0.9.81 | 21 / 1 | |
| 0.9.79 | 21 / 1 | |
| 0.9.77 | 21 / 1 | |
| 0.9.76 | 21 / 1 | |
| 0.9.75 | 21 / 1 | |
| 0.9.71 | 21 / 1 |
v0.9.104
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.103
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.102
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.101
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.100
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.99
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.98
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.97
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.96
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.95
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.94
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.92
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.89
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.88
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.87
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.86
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.81
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.79
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.77
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.76
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.75
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.71
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.