@e-mc/db
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped @e-mc/* package in an established ecosystem; not impersonating pg. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped @e-mc/* package in an established ecosystem; not impersonating qs. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require is used to load DB source clients by name — a documented plugin-loader pattern for this package. | ai |
Versions (showing 51 of 175)
| Version | Deps | Published |
|---|---|---|
| 0.14.5 | 3 / 0 | |
| 0.14.4 | 3 / 0 | |
| 0.14.3 | 3 / 0 | |
| 0.14.2 | 3 / 0 | |
| 0.14.1 | 3 / 0 | |
| 0.14.0 | 3 / 0 | |
| 0.13.11 | 3 / 0 | |
| 0.13.10 | 3 / 0 | |
| 0.13.9 | 3 / 0 | |
| 0.13.8 | 3 / 0 | |
| 0.13.7 | 3 / 0 | |
| 0.13.6 | 3 / 0 | |
| 0.13.5 | 3 / 0 | |
| 0.13.4 | 3 / 0 | |
| 0.13.3 | 3 / 0 | |
| 0.13.2 | 3 / 0 | |
| 0.13.1 | 3 / 0 | |
| 0.13.0 | 3 / 0 | |
| 0.12.17 | 3 / 0 | |
| 0.12.16 | 3 / 0 | |
| 0.12.15 | 3 / 0 | |
| 0.12.14 | 3 / 0 | |
| 0.12.13 | 3 / 0 | |
| 0.12.12 | 3 / 0 | |
| 0.12.11 | 3 / 0 | |
| 0.12.10 | 3 / 0 | |
| 0.12.9 | 3 / 0 | |
| 0.12.8 | 3 / 0 | |
| 0.12.7 | 3 / 0 | |
| 0.12.6 | 3 / 0 | |
| 0.12.5 | 3 / 0 | |
| 0.12.4 | 3 / 0 | |
| 0.12.3 | 3 / 0 | |
| 0.12.2 | 3 / 0 | |
| 0.12.1 | 3 / 0 | |
| 0.12.0 | 3 / 0 | |
| 0.11.18 | 3 / 0 | |
| 0.11.17 | 3 / 0 | |
| 0.11.16 | 3 / 0 | |
| 0.11.15 | 3 / 0 | |
| 0.11.14 | 3 / 0 | |
| 0.11.13 | 3 / 0 | |
| 0.11.12 | 3 / 0 | |
| 0.11.11 | 3 / 0 | |
| 0.11.10 | 3 / 0 | |
| 0.11.9 | 3 / 0 | |
| 0.11.8 | 3 / 0 | |
| 0.11.7 | 3 / 0 | |
| 0.11.5 | 3 / 0 | |
| 0.11.4 | 3 / 0 | |
| 0.11.3 | 3 / 0 |
v0.14.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.