@cubejs-backend/mysql-aurora-serverless-driver
Cube.js Aurora Serverless Mysql database driver
Supply chain provenance
Status for the latest visible version.
Maintainers
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): Large monorepo with SLSA provenance; dormancy explained by release cadence, not account takeover. | ai | |
| provenance | no-provenance | AI (provenance): Established Cube.js monorepo package; provenance absence is consistent across all its versions. | ai | |
| dependencies | unvetted-dep:data-api-client | AI (dependencies): data-api-client is the standard AWS RDS Data API client; expected dependency for an Aurora Serverless driver. | ai | |
| phantom-deps | phantom-dep:@types/mysql | AI (phantom-deps): Type-only dependency loaded by convention; not a real phantom dep for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): README link density reflects monorepo docs style, not a phishing farm; established Cube.js package. | ai |
Versions (showing 45 of 245)
| Version | Deps | Published |
|---|---|---|
| 1.2.23 | 5 / 4 | |
| 1.2.22 | 5 / 4 | |
| 1.2.21 | 5 / 4 | |
| 1.2.20 | 5 / 4 | |
| 1.2.19 | 5 / 4 | |
| 1.2.18 | 5 / 4 | |
| 1.2.17 | 5 / 4 | |
| 1.2.16 | 5 / 4 | |
| 1.2.15 | 5 / 4 | |
| 1.2.14 | 5 / 4 | |
| 1.2.13 | 5 / 4 | |
| 1.2.12 | 5 / 4 | |
| 1.2.11 | 5 / 4 | |
| 1.2.10 | 5 / 4 | |
| 1.2.9 | 5 / 4 | |
| 1.2.8 | 5 / 4 | |
| 1.2.7 | 5 / 4 | |
| 1.2.6 | 5 / 4 | |
| 1.2.5 | 5 / 4 | |
| 1.2.4 | 5 / 4 | |
| 1.2.3 | 5 / 4 | |
| 1.2.2 | 5 / 4 | |
| 1.2.1 | 5 / 4 | |
| 1.2.0 | 5 / 4 | |
| 1.1.17 | 5 / 4 | |
| 1.1.16 | 5 / 4 | |
| 1.1.12 | 5 / 4 | |
| 1.1.10 | 5 / 4 | |
| 1.1.8 | 5 / 4 | |
| 1.1.7 | 5 / 4 | |
| 1.1.4 | 5 / 4 | |
| 1.1.3 | 5 / 4 | |
| 1.1.2 | 5 / 4 | |
| 1.1.1 | 5 / 4 | |
| 1.0.14 | 5 / 4 | |
| 1.0.13 | 5 / 4 | |
| 1.0.12 | 5 / 4 | |
| 1.0.11 | 5 / 4 | |
| 1.0.10 | 5 / 4 | |
| 1.0.9 | 5 / 4 | |
| 1.0.8 | 5 / 4 | |
| 1.0.6 | 5 / 4 | |
| 1.0.3 | 5 / 4 | |
| 1.0.2 | 5 / 4 | |
| 1.0.0 | 5 / 4 |
v1.2.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.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.
v1.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.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.
v1.2.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.
v1.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.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.
v1.2.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.
v1.2.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.
v1.1.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.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.
v1.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.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.
v1.1.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.
v1.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.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.
v1.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.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.
v1.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.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.
v1.0.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.