← Home

@zthun/dalmart-memory

npm Repository Homepage

A set of mock database implementations that use in memory databases for testing.

31
Versions
MIT
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

zthun

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@zthun/helpful-fn AI (phantom-deps): Same-org scope; likely re-exported via barrel or used transitively — stable false positive for this package. ai

Versions (showing 31 of 31)

Version Deps Published
1.6.10 5 / 7
1.6.9 5 / 7
1.6.8 5 / 7
1.6.7 5 / 7
1.6.6 5 / 7
1.6.5 5 / 7
1.6.4 5 / 7
1.6.3 5 / 6
1.6.2 5 / 6
1.6.1 5 / 6
1.6.0 5 / 6
1.5.6 5 / 6
1.5.5 5 / 6
1.5.4 5 / 6
1.5.3 5 / 6
1.5.2 5 / 6
1.5.1 5 / 6
1.5.0 5 / 5
1.4.6 5 / 5
1.4.5 5 / 5
1.4.4 5 / 5
1.4.3 5 / 5
1.4.2 5 / 5
1.4.1 5 / 5
1.3.0 5 / 5
1.2.0 5 / 5
1.1.1 5 / 5
1.1.0 5 / 5
1.0.3 5 / 5
1.0.2 5 / 5
1.0.1 5 / 5

v1.4.6

1 finding
LOW No provenance attestation provenance

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

v1.4.5

1 finding
LOW No provenance attestation provenance

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

v1.4.4

1 finding
LOW No provenance attestation provenance

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

v1.4.3

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.

v1.4.2

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.

v1.4.1

1 finding
LOW No provenance attestation provenance

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

v1.3.0

1 finding
LOW No provenance attestation provenance

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

v1.2.0

1 finding
LOW No provenance attestation provenance

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

v1.1.1

1 finding
LOW No provenance attestation provenance

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

v1.1.0

1 finding
LOW No provenance attestation provenance

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

v1.0.3

1 finding
LOW No provenance attestation provenance

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

v1.0.2

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.

v1.0.1

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.