@cedarjs/gqlorm
Prisma inspired GraphQL query builder
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:core-js | AI (phantom-deps): Polyfill runtime dependency; stable pattern for Babel-compiled packages. | ai | |
| phantom-deps | phantom-dep:@babel/runtime-corejs3 | AI (phantom-deps): Babel runtime helper; implicitly loaded by transpiled code. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Framework library with multi-export API; README/keywords gaps are cosmetic. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): react-dom is a declared peer dependency; phantom-dep false positive for this package. | ai | |
| phantom-deps | phantom-dep:@cedarjs/auth | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic unreliable for monorepo packages. | ai | |
| phantom-deps | phantom-dep:@cedarjs/server-store | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic unreliable for monorepo packages. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 4.2.0 | 4 / 13 | |
| 4.1.0 | 4 / 13 | |
| 4.0.0 | 4 / 13 | |
| 3.1.1 | 6 / 13 | |
| 3.1.0 | 6 / 13 | |
| 3.0.0 | 6 / 13 | |
| 2.8.1 | 8 / 13 | |
| 2.8.0 | 8 / 13 | |
| 2.7.0 | 8 / 13 |
v4.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.