← Home

@cubejs-backend/mysql-aurora-serverless-driver

Cube.js Aurora Serverless Mysql database driver

100
Versions
Apache-2.0
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

cubedevincstatsbotkeydunovmaxim_cube

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 100 of 245)

Version Deps Published
1.4.2 5 / 5
1.4.0 5 / 5
1.3.86 5 / 5
1.3.85 5 / 5
1.3.84 5 / 5
1.3.83 5 / 5
1.3.82 5 / 5
1.3.81 5 / 5
1.3.80 5 / 5
1.3.79 5 / 5
1.3.78 5 / 5
1.3.77 5 / 5
1.3.76 5 / 5
1.3.75 5 / 5
1.3.74 5 / 5
1.3.73 5 / 5
1.3.72 5 / 5
1.3.71 5 / 5
1.3.70 5 / 5
1.3.69 5 / 5
1.3.68 5 / 5
1.3.67 5 / 5
1.3.66 5 / 5
1.3.65 5 / 5
1.3.64 5 / 5
1.3.63 5 / 5
1.3.62 5 / 5
1.3.61 5 / 5
1.3.60 5 / 5
1.3.59 5 / 5
1.3.58 5 / 5
1.3.57 5 / 5
1.3.56 5 / 5
1.3.55 5 / 5
1.3.54 5 / 5
1.3.53 5 / 5
1.3.52 5 / 5
1.3.51 5 / 5
1.3.50 5 / 5
1.3.49 5 / 5
1.3.48 5 / 5
1.3.47 5 / 5
1.3.46 5 / 5
1.3.45 5 / 5
1.3.44 5 / 5
1.3.43 5 / 5
1.3.42 5 / 5
1.3.41 5 / 5
1.3.40 5 / 5
1.3.39 5 / 5
1.3.38 5 / 5
1.3.37 5 / 5
1.3.36 5 / 5
1.3.35 5 / 5
1.3.34 5 / 5
1.3.33 5 / 5
1.3.32 5 / 5
1.3.31 5 / 5
1.3.30 5 / 5
1.3.29 5 / 5
1.3.28 5 / 5
1.3.27 5 / 5
1.3.26 5 / 5
1.3.25 5 / 5
1.3.24 5 / 5
1.3.23 5 / 5
1.3.22 5 / 5
1.3.21 5 / 5
1.3.20 5 / 5
1.3.19 5 / 5
1.3.18 5 / 5
1.3.17 5 / 5
1.3.16 5 / 5
1.3.15 5 / 5
1.3.14 5 / 5
1.3.13 5 / 5
1.3.12 5 / 5
1.3.11 5 / 5
1.3.10 5 / 5
1.3.9 5 / 5
1.3.8 5 / 4
1.3.7 5 / 4
1.3.6 5 / 4
1.3.5 5 / 4
1.3.4 5 / 4
1.3.3 5 / 4
1.3.2 5 / 4
1.3.1 5 / 4
1.3.0 5 / 4
1.2.34 5 / 4
1.2.33 5 / 4
1.2.32 5 / 4
1.2.31 5 / 4
1.2.30 5 / 4
1.2.29 5 / 4
1.2.28 5 / 4
1.2.27 5 / 4
1.2.26 5 / 4
1.2.25 5 / 4
1.2.24 5 / 4
Showing 100 of 245 Next page →

v1.3.10

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.9

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.8

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.7

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.6

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.5

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.4

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.3

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.2

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.2.34

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.2.33

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.2.32

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.2.31

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.2.30

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.2.29

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.2.28

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.2.27

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.2.26

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.2.25

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.2.24

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.