cdk8s
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| vendored-integrity | tampered-vendored-dep:. | AI (vendored-integrity): Flagged files are cdk8s's own package metadata/lib files, not altered projen payload; unchanged across versions. | ai | |
| vendored-integrity | unresolved-vendored-tree:node_modules/follow-redirects | AI (vendored-integrity): Declared bundledDependency; likely version-hash mismatch not implant, from trusted publisher. | ai | |
| vendored-integrity | unresolved-vendored-tree:node_modules/yaml | AI (vendored-integrity): Declared bundledDependency at pinned prerelease version 2.0.0-7; expected hash mismatch. | ai | |
| provenance | publisher-changed | AI (provenance): cdk8s-team migrated publishing to GitHub Actions CI/CD with SLSA attestation; stable pattern going forward. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): cdk8s-core legitimately wraps spawnSync for helm/kubectl invocations; stable pattern across versions. | ai |
Versions (showing 100 of 879)
| Version | Deps | Published |
|---|---|---|
| 2.7.84 | 4 / 23 | |
| 2.7.83 | 4 / 23 | |
| 2.7.82 | 4 / 23 | |
| 2.7.81 | 4 / 23 | |
| 2.7.80 | 4 / 23 | |
| 2.7.79 | 4 / 23 | |
| 2.7.78 | 4 / 23 | |
| 2.7.77 | 4 / 23 | |
| 2.7.76 | 4 / 23 | |
| 2.7.75 | 4 / 23 | |
| 2.7.74 | 4 / 23 | |
| 2.7.73 | 4 / 23 | |
| 2.7.72 | 4 / 23 | |
| 2.7.71 | 4 / 23 | |
| 2.7.70 | 4 / 23 | |
| 2.7.69 | 4 / 23 | |
| 2.7.68 | 4 / 23 | |
| 2.7.67 | 4 / 23 | |
| 2.7.66 | 4 / 23 | |
| 2.7.65 | 4 / 23 | |
| 2.7.64 | 4 / 23 | |
| 2.7.63 | 3 / 23 | |
| 2.7.62 | 3 / 23 | |
| 2.7.61 | 3 / 23 | |
| 2.7.60 | 3 / 23 | |
| 2.7.59 | 3 / 23 | |
| 2.7.58 | 3 / 23 | |
| 2.7.57 | 3 / 23 | |
| 2.7.56 | 3 / 23 | |
| 2.7.55 | 3 / 23 | |
| 2.7.54 | 3 / 23 | |
| 2.7.53 | 3 / 23 | |
| 2.7.52 | 3 / 23 | |
| 2.7.51 | 3 / 23 | |
| 2.7.50 | 3 / 23 | |
| 2.7.49 | 3 / 23 | |
| 2.7.48 | 3 / 23 | |
| 2.7.47 | 3 / 23 | |
| 2.7.46 | 3 / 23 | |
| 2.7.45 | 3 / 23 | |
| 2.7.44 | 3 / 23 | |
| 2.7.43 | 3 / 23 | |
| 2.7.42 | 3 / 23 | |
| 2.7.41 | 3 / 23 | |
| 2.7.40 | 3 / 23 | |
| 2.7.39 | 3 / 23 | |
| 2.7.38 | 3 / 23 | |
| 2.7.37 | 3 / 23 | |
| 2.7.36 | 3 / 23 | |
| 2.7.35 | 3 / 23 | |
| 2.7.34 | 3 / 23 | |
| 2.7.33 | 3 / 23 | |
| 2.7.32 | 3 / 23 | |
| 2.7.31 | 3 / 23 | |
| 2.7.30 | 3 / 23 | |
| 2.7.29 | 3 / 23 | |
| 2.7.28 | 3 / 23 | |
| 2.7.27 | 3 / 23 | |
| 2.7.26 | 3 / 23 | |
| 2.7.25 | 3 / 23 | |
| 2.7.24 | 3 / 23 | |
| 2.7.23 | 3 / 23 | |
| 2.7.22 | 3 / 23 | |
| 2.7.21 | 3 / 23 | |
| 2.7.20 | 3 / 23 | |
| 2.7.19 | 3 / 23 | |
| 2.7.18 | 3 / 23 | |
| 2.7.17 | 3 / 23 | |
| 2.7.16 | 3 / 23 | |
| 2.7.15 | 3 / 23 | |
| 2.7.14 | 3 / 23 | |
| 2.7.13 | 3 / 23 | |
| 2.7.12 | 3 / 23 | |
| 2.7.11 | 3 / 23 | |
| 2.7.10 | 3 / 23 | |
| 2.7.9 | 3 / 23 | |
| 2.7.8 | 3 / 23 | |
| 2.7.7 | 3 / 23 | |
| 2.7.6 | 3 / 22 | |
| 2.7.5 | 3 / 22 | |
| 2.7.4 | 3 / 22 | |
| 2.7.3 | 3 / 22 | |
| 2.7.2 | 3 / 22 | |
| 2.7.1 | 3 / 22 | |
| 2.7.0 | 3 / 22 | |
| 2.6.49 | 3 / 22 | |
| 2.6.48 | 3 / 22 | |
| 2.6.47 | 3 / 22 | |
| 2.6.46 | 3 / 22 | |
| 2.6.45 | 3 / 22 | |
| 2.6.44 | 3 / 22 | |
| 2.6.43 | 3 / 22 | |
| 2.6.42 | 3 / 22 | |
| 2.6.41 | 3 / 22 | |
| 2.6.40 | 3 / 22 | |
| 2.6.39 | 3 / 22 | |
| 2.6.38 | 3 / 22 | |
| 2.6.37 | 3 / 22 | |
| 2.6.36 | 3 / 22 | |
| 2.6.35 | 3 / 22 |
v2.7.84
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.83
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.82
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.81
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.80
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.79
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.78
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.77
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.76
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.75
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.74
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.73
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.72
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.71
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.70
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.69
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.68
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.67
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.66
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.65
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.64
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.63
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.62
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.61
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.60
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.59
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.58
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.57
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.