← Home

@possumtech/sqlrite

npm Repository Homepage
25
Versions
—
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

possumtechcom

Keywords

nodesqlitenode-sqlitesqlsql-firstzero-dependencywalormdatabase

Versions (showing 25 of 25)

Version Deps Published
6.5.0 0 / 3
6.4.1 0 / 3
6.4.0 0 / 3
6.3.0 0 / 3
6.1.0 0 / 3
5.2.0 0 / 3
5.1.1 0 / 3
5.1.0 0 / 3
5.0.0 0 / 3
4.0.0 0 / 3
3.1.0 0 / 1
3.0.0 0 / 1
2.6.0 0 / 1
2.5.0 0 / 1
2.4.0 0 / 1
2.3.0 0 / 1
2.2.0 0 / 1
2.1.0 0 / 1
2.0.4 0 / 1
2.0.3 0 / 1
2.0.2 0 / 1
2.0.1 0 / 1
1.1.1 0 / 1
1.1.0 0 / 1
1.0.2 0 / 1

v6.5.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v6.4.1

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v6.4.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v6.3.0

2 findings
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

INFO Publisher changed: possumtechcom → GitHub Actions (on 2026-07-19, now via trusted publisher with provenance) provenance

This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (possumtechcom) on 2026-07-19, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.

v6.1.0

2 findings
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

INFO Publisher changed: possumtechcom → GitHub Actions (on 2026-07-19, now via trusted publisher with provenance) provenance

This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (possumtechcom) on 2026-07-19, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.