@cedarjs/cli-helpers
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Established monorepo package; sparse README is typical for internal tooling packages. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): lodash is declared as a runtime dep and used in config/build context; phantom-dep heuristic fires on config references. | ai | |
| phantom-deps | phantom-dep:prompts | AI (phantom-deps): prompts declared as runtime dep; phantom-dep fires on config references, not a real missing-import issue. | ai | |
| phantom-deps | phantom-dep:enquirer | AI (phantom-deps): enquirer declared as runtime dep; phantom-dep fires on config references, stable false positive for this package. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 4.2.0 | 19 / 11 | |
| 4.1.0 | 19 / 11 | |
| 4.0.0 | 19 / 11 | |
| 3.1.1 | 19 / 11 | |
| 3.1.0 | 19 / 11 | |
| 3.0.0 | 19 / 11 | |
| 2.8.1 | 19 / 11 | |
| 2.8.0 | 19 / 11 | |
| 2.7.0 | 17 / 11 | |
| 2.6.0 | 17 / 11 | |
| 2.5.1 | 17 / 11 | |
| 2.5.0 | 17 / 11 | |
| 2.4.1 | 17 / 11 | |
| 2.4.0 | 17 / 11 | |
| 2.3.0 | 17 / 11 | |
| 2.2.1 | 17 / 11 | |
| 2.2.0 | 17 / 11 | |
| 2.1.1 | 17 / 11 | |
| 2.1.0 | 17 / 11 | |
| 2.0.3 | 17 / 11 | |
| 2.0.2 | 17 / 11 | |
| 2.0.1 | 17 / 11 | |
| 2.0.0 | 17 / 11 | |
| 1.1.2 | 17 / 11 | |
| 1.1.1 | 17 / 11 | |
| 1.1.0 | 17 / 11 | |
| 1.0.0 | 17 / 11 |
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. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
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.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.