@dbcube/core
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped @dbcube/core is a database ORM, not a typosquat of the cors middleware; name collision is coincidental. | ai |
Versions (showing 48 of 48)
| Version | Deps | Published |
|---|---|---|
| 5.1.13 | 5 / 7 | |
| 5.1.12 | 5 / 7 | |
| 5.1.11 | 5 / 7 | |
| 5.1.10 | 5 / 7 | |
| 5.1.9 | 5 / 7 | |
| 5.1.4 | 5 / 6 | |
| 5.0.13 | 5 / 6 | |
| 5.0.12 | 5 / 6 | |
| 5.0.11 | 5 / 6 | |
| 5.0.10 | 5 / 6 | |
| 5.0.9 | 5 / 6 | |
| 5.0.8 | 5 / 6 | |
| 5.0.7 | 5 / 6 | |
| 5.0.6 | 5 / 6 | |
| 5.0.5 | 5 / 6 | |
| 5.0.4 | 5 / 6 | |
| 5.0.3 | 5 / 6 | |
| 5.0.2 | 5 / 6 | |
| 5.0.1 | 5 / 6 | |
| 4.1.21 | 5 / 6 | |
| 4.1.20 | 5 / 6 | |
| 4.1.19 | 5 / 6 | |
| 4.1.18 | 5 / 6 | |
| 4.1.17 | 5 / 6 | |
| 4.1.16 | 5 / 6 | |
| 4.1.15 | 5 / 6 | |
| 4.1.14 | 5 / 6 | |
| 4.1.13 | 5 / 6 | |
| 4.1.12 | 5 / 6 | |
| 4.1.11 | 5 / 6 | |
| 4.1.10 | 5 / 6 | |
| 4.1.9 | 5 / 6 | |
| 4.1.8 | 5 / 6 | |
| 4.1.7 | 5 / 6 | |
| 4.1.6 | 5 / 6 | |
| 4.1.5 | 5 / 6 | |
| 4.1.4 | 5 / 6 | |
| 4.0.4 | 5 / 6 | |
| 4.0.3 | 5 / 6 | |
| 4.0.2 | 5 / 6 | |
| 4.0.1 | 5 / 6 | |
| 3.2.8 | 5 / 6 | |
| 3.2.7 | 5 / 6 | |
| 3.2.6 | 5 / 6 | |
| 3.2.5 | 5 / 6 | |
| 3.2.4 | 5 / 6 | |
| 3.2.3 | 5 / 6 | |
| 3.2.2 | 5 / 6 |
v5.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.12
2 findingsPackage name '@dbcube/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.11
2 findingsPackage name '@dbcube/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.10
2 findingsPackage name '@dbcube/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.9
2 findingsPackage name '@dbcube/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.4
2 findingsPackage name '@dbcube/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.13
2 findingsPackage name '@dbcube/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.12
2 findingsPackage name '@dbcube/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.11
2 findingsPackage name '@dbcube/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.10
2 findingsPackage name '@dbcube/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.9
2 findingsPackage name '@dbcube/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.8
2 findingsPackage name '@dbcube/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.7
2 findingsPackage name '@dbcube/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.6
2 findingsPackage name '@dbcube/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.5
2 findingsPackage name '@dbcube/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.4
2 findingsPackage name '@dbcube/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.3
2 findingsPackage name '@dbcube/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.2
2 findingsPackage name '@dbcube/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.1
2 findingsPackage name '@dbcube/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.21
2 findingsPackage name '@dbcube/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.20
2 findingsPackage name '@dbcube/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.19
2 findingsPackage name '@dbcube/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.18
2 findingsPackage name '@dbcube/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.17
2 findingsPackage name '@dbcube/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.16
2 findingsPackage name '@dbcube/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.15
2 findingsPackage name '@dbcube/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.14
2 findingsPackage name '@dbcube/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.13
2 findingsPackage name '@dbcube/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.12
2 findingsPackage name '@dbcube/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.11
2 findingsPackage name '@dbcube/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.10
2 findingsPackage name '@dbcube/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.9
2 findingsPackage name '@dbcube/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.8
2 findingsPackage name '@dbcube/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.7
2 findingsPackage name '@dbcube/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.6
2 findingsPackage name '@dbcube/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.5
2 findingsPackage name '@dbcube/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.4
2 findingsPackage name '@dbcube/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.4
2 findingsPackage name '@dbcube/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.3
2 findingsPackage name '@dbcube/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.2
2 findingsPackage name '@dbcube/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
2 findingsPackage name '@dbcube/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.8
2 findingsPackage name '@dbcube/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.7
2 findingsPackage name '@dbcube/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.6
2 findingsPackage name '@dbcube/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.5
2 findingsPackage name '@dbcube/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.4
2 findingsPackage name '@dbcube/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.3
2 findingsPackage name '@dbcube/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.2
2 findingsPackage name '@dbcube/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.