@bimetal/store-eventstoredb
EventStoreDB-backed EventStore implementation for @bimetal/data — native event sourcing
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@bimetal/event-sourcing | AI (dependencies): Same-org dependency matching the package's documented event-sourcing purpose; consistent with prior @bimetal namespace packages. | ai | |
| provenance | no-provenance | AI (provenance): New package from a small org; absence of Sigstore attestation is common and not a risk signal here. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 0.35.0 | 2 / 1 | |
| 0.34.0 | 2 / 1 | |
| 0.32.0 | 2 / 1 | |
| 0.30.0 | 2 / 1 | |
| 0.29.0 | 2 / 1 | |
| 0.17.0 | 2 / 1 | |
| 0.16.7 | 2 / 1 | |
| 0.16.1 | 2 / 1 | |
| 0.15.10 | 2 / 1 | |
| 0.15.3 | 2 / 1 | |
| 0.14.1 | 2 / 1 | |
| 0.13.6 | 2 / 1 | |
| 0.13.5 | 2 / 1 | |
| 0.13.4 | 2 / 1 | |
| 0.13.3 | 2 / 1 | |
| 0.13.2 | 2 / 1 | |
| 0.13.0 | 2 / 1 | |
| 0.11.0 | 2 / 1 | |
| 0.10.0 | 2 / 1 | |
| 0.9.1 | 2 / 1 | |
| 0.9.0 | 2 / 1 | |
| 0.6.0 | 2 / 1 | |
| 0.1.0 | 2 / 1 |
v0.35.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.