@cedarjs/cli
The CedarJS Command Line
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:joi | AI (typosquat): @cedarjs/cli is a scoped framework package; levenshtein match to 'joi' is a false positive. | ai | |
| phantom-deps | phantom-dep:prisma | AI (phantom-deps): CLI tool invoked by convention in a framework context, not directly imported. | ai | |
| phantom-deps | phantom-dep:recast | AI (phantom-deps): Referenced in config/build tooling, not a direct import — stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:rimraf | AI (phantom-deps): CLI utility used in scripts/config, not directly imported — stable false positive. | ai | |
| phantom-deps | phantom-dep:unionfs | AI (phantom-deps): Used in test/config context by convention; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:cross-env | AI (phantom-deps): CLI env utility used in scripts, not directly imported — stable false positive. | ai | |
| phantom-deps | phantom-dep:@cedarjs/fastify-web | AI (phantom-deps): Same-org sibling package loaded by convention in framework context. | ai | |
| phantom-deps | phantom-dep:@babel/preset-typescript | AI (phantom-deps): Framework-scoped Babel preset loaded by convention, not direct import — stable false positive. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 4.2.0 | 59 / 9 | |
| 4.1.0 | 59 / 9 | |
| 4.0.0 | 59 / 9 | |
| 3.1.1 | 59 / 9 | |
| 3.1.0 | 59 / 9 | |
| 3.0.0 | 59 / 9 | |
| 2.8.1 | 61 / 9 | |
| 2.8.0 | 61 / 9 | |
| 2.7.0 | 60 / 9 | |
| 2.6.0 | 60 / 9 | |
| 2.5.1 | 58 / 9 | |
| 2.5.0 | 58 / 9 | |
| 2.4.1 | 57 / 9 | |
| 2.4.0 | 57 / 9 | |
| 2.3.0 | 57 / 9 | |
| 2.2.1 | 57 / 9 | |
| 2.2.0 | 58 / 9 | |
| 2.1.1 | 58 / 8 | |
| 2.1.0 | 58 / 8 | |
| 2.0.3 | 58 / 8 | |
| 2.0.2 | 58 / 8 | |
| 2.0.1 | 58 / 8 | |
| 2.0.0 | 58 / 8 | |
| 1.1.2 | 58 / 8 | |
| 1.1.1 | 58 / 8 | |
| 1.1.0 | 58 / 8 | |
| 1.0.0 | 58 / 8 |
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. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. 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.