@cedarjs/codemods
Codemods to ease upgrading a CedarJS Project
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:tasuku | AI (dependencies): tasuku is a well-known task runner UI library; its use in a codemods CLI is expected and benign. | ai | |
| provenance | no-provenance | AI (provenance): CedarJS monorepo package; provenance absence is consistent across all versions and not a risk indicator here. | ai | |
| phantom-deps | phantom-dep:deepmerge | AI (phantom-deps): Declared in dependencies and used via config convention in a framework codemod package; stable FP. | ai | |
| phantom-deps | phantom-dep:@babel/cli | AI (phantom-deps): Framework-scoped babel tooling loaded by convention; stable FP for this package. | ai | |
| phantom-deps | phantom-dep:@svgr/plugin-jsx | AI (phantom-deps): Plugin loaded by @svgr/core at runtime via config; stable FP. | ai | |
| phantom-deps | phantom-dep:@babel/plugin-transform-typescript | AI (phantom-deps): Babel plugin loaded by convention via babel config; stable FP. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 4.2.0 | 22 / 9 | |
| 4.1.0 | 22 / 9 | |
| 4.0.0 | 22 / 9 | |
| 3.1.1 | 22 / 9 | |
| 3.1.0 | 22 / 9 | |
| 3.0.0 | 22 / 9 | |
| 2.8.1 | 23 / 9 | |
| 2.8.0 | 23 / 9 | |
| 2.7.0 | 23 / 9 | |
| 2.6.0 | 23 / 7 | |
| 2.5.1 | 23 / 7 | |
| 2.5.0 | 23 / 7 | |
| 2.4.1 | 23 / 7 | |
| 2.4.0 | 23 / 7 | |
| 2.3.0 | 23 / 7 | |
| 2.2.1 | 23 / 7 | |
| 2.2.0 | 23 / 9 | |
| 2.1.1 | 23 / 10 | |
| 2.1.0 | 23 / 10 | |
| 2.0.3 | 23 / 10 | |
| 2.0.2 | 23 / 10 | |
| 2.0.1 | 23 / 10 | |
| 2.0.0 | 23 / 10 | |
| 1.1.2 | 23 / 10 | |
| 1.1.1 | 23 / 10 | |
| 1.1.0 | 23 / 10 | |
| 1.0.0 | 23 / 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.
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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.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.
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.