@builderbot/database-mysql
Esto es el conector a Mysql
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package; thin README and no keywords are typical for internal connectors, not spam. | ai | |
| dependencies | unvetted-dep:@builderbot/bot | AI (dependencies): Sibling package in the same builderbot monorepo; intra-ecosystem dependency, not a third-party risk. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 1.4.1 | 2 / 11 | |
| 1.4.0 | 2 / 11 | |
| 1.3.15 | 2 / 11 | |
| 1.3.14 | 2 / 11 | |
| 1.3.13 | 2 / 11 | |
| 1.3.12 | 2 / 11 | |
| 1.3.11 | 2 / 11 | |
| 1.3.10 | 2 / 11 | |
| 1.3.8 | 2 / 11 | |
| 1.3.7 | 2 / 11 | |
| 1.3.5 | 2 / 11 | |
| 1.3.4 | 2 / 11 | |
| 1.3.3 | 2 / 11 | |
| 1.3.1 | 2 / 11 | |
| 1.2.9 | 2 / 11 | |
| 1.2.8 | 2 / 11 | |
| 1.2.7 | 2 / 11 | |
| 1.2.6 | 2 / 11 |
v1.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.