@cubejs-backend/server
Cube.js all-in-one server
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@cubejs-backend/dotenv | AI (dependencies): Same-org scoped fork of dotenv; stable dependency pattern across Cube.js monorepo versions. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): SLSA provenance attestation and no material changes vs prior version mitigate account-takeover concern for this established monorepo package. | ai | |
| phantom-deps | phantom-dep:@oclif/config | AI (phantom-deps): oclif config loaded via manifest/plugin system, not direct import; stable FP. | ai | |
| phantom-deps | phantom-dep:codesandbox-import-utils | AI (phantom-deps): Likely used indirectly via server-core or dynamic require; stable FP for this package. | ai | |
| phantom-deps | phantom-dep:@cubejs-backend/cubestore-driver | AI (phantom-deps): Same-org dep loaded dynamically; stable FP for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@oclif/plugin-help | AI (phantom-deps): Declared as oclif plugin in package.json oclif.plugins; loaded by framework, not direct import. | ai | |
| phantom-deps | phantom-dep:jsonwebtoken | AI (phantom-deps): Used via oclif CLI/config indirection, not direct import; stable FP for this package. | ai | |
| typosquat | typosquat.levenshtein:semver | AI (typosquat): Legitimate Cube.js monorepo package; not a typosquat of semver — Levenshtein match is coincidental. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established Cube.js ecosystem package; sparse README is a documentation issue, not a spam/bogus signal. | ai |
Versions (showing 25 of 126)
| Version | Deps | Published |
|---|---|---|
| 1.1.12 | 19 / 12 | |
| 1.1.11 | 19 / 12 | |
| 1.1.10 | 19 / 12 | |
| 1.1.9 | 19 / 12 | |
| 1.1.8 | 19 / 12 | |
| 1.1.7 | 19 / 12 | |
| 1.1.6 | 19 / 12 | |
| 1.1.5 | 19 / 12 | |
| 1.1.4 | 19 / 12 | |
| 1.1.3 | 19 / 12 | |
| 1.1.2 | 19 / 12 | |
| 1.1.1 | 19 / 12 | |
| 1.1.0 | 19 / 12 | |
| 1.0.12 | 19 / 12 | |
| 1.0.11 | 19 / 12 | |
| 1.0.10 | 19 / 12 | |
| 1.0.9 | 19 / 12 | |
| 1.0.8 | 19 / 12 | |
| 1.0.6 | 19 / 12 | |
| 1.0.5 | 19 / 12 | |
| 1.0.4 | 19 / 12 | |
| 1.0.3 | 19 / 12 | |
| 1.0.2 | 19 / 12 | |
| 1.0.1 | 19 / 12 | |
| 1.0.0 | 19 / 12 |
v1.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.