@epicdm/flowstate-rxdb-node-client
RxDB D1 replication client for Node.js services — real-time database event streams
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Consistent across all versions of this package; publisher has clean track record. | ai | |
| dependencies | unvetted-dep:@epicdm/flowstate-rxdb | AI (dependencies): Internal monorepo workspace dep; resolves to publisher's own package at publish time. | ai | |
| dependencies | unvetted-dep:@epicdm/flowstate-rxdb-d1 | AI (dependencies): Internal monorepo workspace dep; resolves to publisher's own package at publish time. | ai | |
| dependencies | unvetted-dep:@epicdm/flowstate-collections | AI (dependencies): Internal monorepo workspace dep; resolves to publisher's own package at publish time. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 1.0.7 | 4 / 9 | |
| 1.0.6 | 4 / 9 | |
| 1.0.5 | 4 / 9 | |
| 1.0.4 | 4 / 9 | |
| 1.0.3 | 4 / 9 | |
| 1.0.2 | 4 / 9 | |
| 1.0.1 | 4 / 9 | |
| 1.0.0 | 4 / 9 |
v1.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.