← Home

@bimetal/store-sqlite

npm Repository Homepage

SQLite EventStore implementation for @bimetal/data — file-based, zero-config persistence

7
Versions
PolyForm-Noncommercial-1.0.0
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

biederbe

Keywords

calendarevent-sourcingsqlitepersistenceeventstore

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@bimetal/event-sourcing AI (dependencies): Internal @bimetal monorepo package; consistent with the package's stated purpose and the dep swap from @bimetal/data. ai
provenance no-provenance AI (provenance): New package family without provenance setup; not a security signal for this package. ai

Versions (showing 7 of 7)

Version Deps Published
0.13.0 2 / 3
0.11.0 2 / 2
0.10.0 2 / 2
0.9.1 2 / 2
0.9.0 2 / 2
0.6.0 2 / 2
0.1.0 2 / 2

v0.13.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.11.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.10.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.6.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.