@contractspec/lib.runtime-sandbox
**Browser-compatible database abstraction built on PGLite for client-side SQL execution.**
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 51 of 53)
| Version | Deps | Published |
|---|---|---|
| 3.0.8 | 1 / 9 | |
| 3.0.7 | 1 / 9 | |
| 3.0.6 | 1 / 9 | |
| 3.0.5 | 1 / 9 | |
| 3.0.4 | 1 / 9 | |
| 3.0.3 | 1 / 9 | |
| 3.0.2 | 1 / 9 | |
| 3.0.1 | 1 / 9 | |
| 3.0.0 | 1 / 9 | |
| 2.7.15 | 4 / 6 | |
| 2.7.14 | 3 / 6 | |
| 2.7.13 | 3 / 6 | |
| 2.7.12 | 3 / 6 | |
| 2.7.11 | 3 / 6 | |
| 2.7.10 | 3 / 6 | |
| 2.7.9 | 3 / 6 | |
| 2.7.6 | 3 / 6 | |
| 2.7.5 | 3 / 6 | |
| 2.7.4 | 3 / 6 | |
| 2.7.1 | 3 / 6 | |
| 2.7.0 | 3 / 6 | |
| 2.6.0 | 3 / 6 | |
| 2.5.5 | 3 / 6 | |
| 2.5.4 | 3 / 6 | |
| 2.5.3 | 3 / 6 | |
| 2.5.2 | 3 / 6 | |
| 2.5.0 | 3 / 6 | |
| 2.4.3 | 3 / 6 | |
| 2.4.2 | 3 / 6 | |
| 2.4.1 | 3 / 6 | |
| 2.4.0 | 3 / 6 | |
| 2.3.0 | 3 / 6 | |
| 2.2.0 | 3 / 6 | |
| 2.1.0 | 3 / 6 | |
| 2.0.0 | 3 / 6 | |
| 1.9.0 | 3 / 6 | |
| 1.8.0 | 3 / 6 | |
| 1.7.0 | 3 / 6 | |
| 1.6.0 | 3 / 6 | |
| 1.5.0 | 3 / 6 | |
| 1.4.0 | 3 / 6 | |
| 1.3.0 | 3 / 6 | |
| 1.2.0 | 3 / 6 | |
| 1.1.0 | 3 / 6 | |
| 1.0.0 | 3 / 6 | |
| 0.17.0 | 3 / 6 | |
| 0.16.0 | 3 / 6 | |
| 0.15.0 | 3 / 6 | |
| 0.14.0 | 3 / 6 | |
| 0.13.0 | 3 / 6 | |
| 0.12.0 | 3 / 7 |
v3.0.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.7.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.7.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.7.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.7.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.7.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.7.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.7.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.7.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.7.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
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.
v0.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.