@live-change/db-store-lmdb
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:node-lmdb | AI (dependencies): node-lmdb is the canonical LMDB native binding; expected and appropriate for this DB store package. | ai | |
| phantom-deps | phantom-dep:p-queue | AI (phantom-deps): Declared as runtime dep for async queuing; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:napi-macros | AI (phantom-deps): napi-macros is a native build tool dependency; not directly imported in JS but legitimately declared. | ai |
Versions (showing 51 of 96)
| Version | Deps | Published |
|---|---|---|
| 0.9.209 | 5 / 2 | |
| 0.9.207 | 5 / 2 | |
| 0.9.204 | 5 / 2 | |
| 0.9.203 | 5 / 2 | |
| 0.9.201 | 5 / 2 | |
| 0.9.200 | 5 / 2 | |
| 0.9.198 | 5 / 2 | |
| 0.9.197 | 5 / 2 | |
| 0.9.196 | 5 / 2 | |
| 0.9.195 | 5 / 2 | |
| 0.9.193 | 5 / 2 | |
| 0.9.191 | 5 / 2 | |
| 0.9.189 | 5 / 2 | |
| 0.9.188 | 5 / 2 | |
| 0.9.186 | 5 / 2 | |
| 0.9.185 | 5 / 2 | |
| 0.9.183 | 5 / 2 | |
| 0.9.181 | 5 / 2 | |
| 0.9.180 | 5 / 2 | |
| 0.9.179 | 5 / 2 | |
| 0.9.178 | 5 / 2 | |
| 0.9.177 | 5 / 2 | |
| 0.9.176 | 5 / 2 | |
| 0.9.175 | 5 / 2 | |
| 0.9.174 | 5 / 2 | |
| 0.9.171 | 5 / 2 | |
| 0.9.169 | 5 / 2 | |
| 0.9.167 | 5 / 2 | |
| 0.9.166 | 5 / 2 | |
| 0.9.165 | 5 / 2 | |
| 0.9.164 | 5 / 2 | |
| 0.9.163 | 5 / 2 | |
| 0.9.162 | 5 / 2 | |
| 0.9.161 | 5 / 2 | |
| 0.9.160 | 5 / 2 | |
| 0.9.159 | 5 / 2 | |
| 0.9.158 | 5 / 2 | |
| 0.9.155 | 5 / 2 | |
| 0.9.154 | 5 / 2 | |
| 0.9.153 | 5 / 2 | |
| 0.9.151 | 5 / 2 | |
| 0.9.150 | 5 / 2 | |
| 0.9.147 | 5 / 2 | |
| 0.9.146 | 5 / 2 | |
| 0.9.145 | 5 / 2 | |
| 0.9.144 | 5 / 2 | |
| 0.9.143 | 5 / 2 | |
| 0.9.139 | 5 / 2 | |
| 0.9.138 | 5 / 2 | |
| 0.9.136 | 5 / 2 | |
| 0.9.133 | 5 / 2 |
v0.9.209
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.207
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.203
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.201
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.200
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.198
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.197
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.196
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.195
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.193
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.191
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.189
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.188
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.186
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.185
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.183
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.181
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.180
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.179
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.178
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.177
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.176
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.175
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.174
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.171
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.169
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.167
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.166
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.165
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.164
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.163
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.162
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.161
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.160
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.159
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.158
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.155
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.154
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.153
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.151
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.150
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.147
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.146
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.145
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.144
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.143
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.139
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.138
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.136
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.133
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.