@trayio/cdk-cli-commons
Shared utils between CDK ClIs
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:@oclif/test | AI (dependencies): @oclif/test is a well-known oclif framework testing utility; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Org-published scoped package; no provenance is consistent across all 36 versions and poses no direct security risk. | ai | |
| phantom-deps | phantom-dep:@oclif/test | AI (phantom-deps): Referenced in config files per finding; not a real import gap for this package. | ai | |
| phantom-deps | phantom-dep:@trayio/axios | AI (phantom-deps): Same org scope; likely re-exported or used indirectly; stable false positive for this package. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 5.26.0 | 6 / 0 | |
| 5.25.0 | 6 / 0 | |
| 5.24.0 | 6 / 0 | |
| 5.23.0 | 6 / 0 | |
| 5.22.0 | 6 / 0 | |
| 5.21.0 | 6 / 0 | |
| 5.20.0 | 6 / 0 | |
| 5.19.0 | 6 / 0 | |
| 5.18.0 | 6 / 0 | |
| 5.17.0 | 6 / 0 | |
| 5.16.0 | 6 / 0 | |
| 5.15.0 | 6 / 0 | |
| 5.14.0 | 6 / 0 | |
| 5.13.0 | 6 / 0 | |
| 5.12.0 | 6 / 0 | |
| 5.11.0 | 6 / 0 | |
| 5.10.0 | 6 / 0 | |
| 5.9.0 | 6 / 0 | |
| 5.8.0 | 6 / 0 | |
| 5.7.0 | 6 / 0 | |
| 5.6.0 | 6 / 0 | |
| 5.5.0 | 6 / 0 | |
| 4.104.0 | 6 / 0 |
v5.26.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.25.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.24.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.23.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.22.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.104.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.