mariadb
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/callback.cjs | AI (source-diff): esbuild --minify CJS bundle; build script is in package.json. Stable for this package. | ai | |
| source-diff | obfuscated-file:dist/promise.cjs | AI (source-diff): esbuild --minify CJS bundle; build script is in package.json. Stable for this package. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding in parsec-auth.js is standard PARSEC/SCRAM authentication protocol handling — parsing a server-provided salt. Not a malicious payload; stable for this database connector package. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): @types/node is listed as a runtime dep to expose TypeScript types to consumers; not directly imported at runtime. Standard pattern for this connector. | ai | |
| phantom-deps | phantom-dep:@types/geojson | AI (phantom-deps): @types/geojson provides GeoJSON type definitions for the connector's spatial data support; not directly imported at runtime. Standard pattern for this connector. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 3.5.3 | 5 / 14 | |
| 3.5.2 | 5 / 14 | |
| 3.5.1 | 3 / 14 | |
| 3.4.5 | 5 / 16 | |
| 3.4.4 | 3 / 18 | |
| 3.4.3 | 3 / 18 | |
| 3.4.2 | 5 / 16 |
v3.5.3
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.