@hedystia/db
Next-gen TypeScript ORM for building type-safe database layers at lightspeed
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Package has SLSA attestation; missing gitHead is a minor metadata gap, not a supply chain risk. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped ORM package with distinct identity; Levenshtein match to 'pg' is coincidental. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped ORM package with distinct identity; Levenshtein match to 'qs' is coincidental. | ai |
Versions (showing 45 of 45)
| Version | Deps | Published |
|---|---|---|
| 2.3.23 | 0 / 2 | |
| 2.3.22 | 0 / 2 | |
| 2.3.21 | 0 / 2 | |
| 2.3.20 | 0 / 2 | |
| 2.3.19 | 0 / 2 | |
| 2.3.18 | 0 / 2 | |
| 2.3.17 | 0 / 2 | |
| 2.3.9 | 0 / 2 | |
| 2.3.8 | 0 / 2 | |
| 2.3.7 | 0 / 2 | |
| 2.3.6 | 0 / 2 | |
| 2.3.5 | 0 / 2 | |
| 2.3.4 | 0 / 2 | |
| 2.3.3 | 0 / 2 | |
| 2.3.2 | 0 / 2 | |
| 2.3.1 | 0 / 2 | |
| 2.2.13 | 0 / 2 | |
| 2.2.12 | 0 / 2 | |
| 2.2.11 | 0 / 2 | |
| 2.2.9 | 0 / 2 | |
| 2.2.8 | 0 / 2 | |
| 2.2.7 | 0 / 2 | |
| 2.2.6 | 0 / 2 | |
| 2.2.5 | 0 / 2 | |
| 2.2.4 | 0 / 2 | |
| 2.2.3 | 0 / 2 | |
| 2.2.2 | 0 / 2 | |
| 2.2.1 | 0 / 2 | |
| 2.2.0 | 0 / 2 | |
| 2.1.1 | 0 / 1 | |
| 2.1.0 | 0 / 1 | |
| 2.0.14 | 0 / 1 | |
| 2.0.13 | 0 / 1 | |
| 2.0.12 | 0 / 1 | |
| 2.0.11 | 0 / 1 | |
| 2.0.10 | 0 / 1 | |
| 2.0.9 | 0 / 1 | |
| 2.0.8 | 0 / 1 | |
| 2.0.7 | 0 / 1 | |
| 2.0.6 | 0 / 1 | |
| 2.0.5 | 0 / 1 | |
| 2.0.4 | 0 / 1 | |
| 2.0.3 | 0 / 1 | |
| 2.0.2 | 0 / 1 | |
| 2.0.1 | 0 / 1 |
v2.3.23
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.3.22
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: zastinian.
v2.3.21
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: zastinian.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.3.20
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: zastinian.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.3.19
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: zastinian.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.3.18
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: zastinian.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.3.17
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.