@cedarjs/api-server
CedarJS's HTTP server for Serverless Functions
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:picoquery | AI (dependencies): picoquery is a legitimate qs replacement; intentional dep swap in this version. | ai | |
| phantom-deps | phantom-dep:chalk | AI (phantom-deps): chalk is a declared runtime dependency; phantom-dep fires because it's used indirectly via config, not a real issue. | ai | |
| dependencies | unvetted-dep:@fastify/url-data | AI (dependencies): @fastify/url-data is an official Fastify organization plugin; no security concerns. | ai | |
| provenance | no-provenance | AI (provenance): Established CedarJS framework package; provenance absence is consistent across all versions. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 4.2.0 | 21 / 11 | |
| 4.1.0 | 24 / 11 | |
| 3.1.1 | 19 / 11 | |
| 3.0.0 | 19 / 11 | |
| 2.8.0 | 19 / 12 | |
| 2.5.1 | 19 / 11 | |
| 2.4.1 | 19 / 11 | |
| 2.4.0 | 19 / 11 | |
| 2.3.0 | 19 / 11 | |
| 2.2.1 | 19 / 11 | |
| 2.1.1 | 19 / 11 | |
| 2.1.0 | 19 / 11 | |
| 2.0.3 | 19 / 11 | |
| 2.0.2 | 19 / 11 | |
| 2.0.1 | 19 / 11 | |
| 2.0.0 | 19 / 11 | |
| 1.1.1 | 19 / 10 | |
| 1.0.0 | 19 / 10 |
v4.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.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.
v2.8.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.
v2.5.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.
v2.4.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.
v2.4.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.
v2.3.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.
v2.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.
v2.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.
v2.1.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.
v2.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.
v2.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.
v2.0.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.
v2.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.
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.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.