@pi-r/mariadb
MariaDB client driver for E-mc.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Established package with 64 versions and consistent repo; long gap without other malware indicators is low risk. | ai | |
| dependencies | unvetted-dep:@e-mc/db | AI (dependencies): Same-author org dependency from anpham6/pi-r monorepo; stable companion across versions. | ai | |
| dependencies | unvetted-dep:@e-mc/types | AI (dependencies): Same-author org types dependency from anpham6/pi-r monorepo; stable companion across versions. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across all 63 versions; author has not adopted Sigstore attestation but package is otherwise clean. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 0.12.0 | 3 / 0 | |
| 0.11.3 | 3 / 0 | |
| 0.11.2 | 3 / 0 | |
| 0.11.1 | 3 / 0 | |
| 0.11.0 | 3 / 0 | |
| 0.10.4 | 3 / 0 | |
| 0.10.3 | 3 / 0 | |
| 0.10.2 | 3 / 0 | |
| 0.10.1 | 3 / 0 | |
| 0.10.0 | 3 / 0 | |
| 0.9.5 | 3 / 0 | |
| 0.8.5 | 3 / 0 | |
| 0.7.6 | 3 / 0 | |
| 0.6.10 | 3 / 0 |
v0.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.