@pipeline-builder/pipeline-core
AWS CDK construct library for Pipeline Builder: the Builder construct that assembles plugin specs into a CodePipeline stack, PluginLookup custom resource, pipeline/plugin domain types, and shared configuration.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decode is used to deserialize structured plugin config data with immediate JSON parsing and strict schema validation — a legitimate pattern for this AWS CDK plugin lookup construct. | ai | |
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): uuid is explicitly declared in dependencies and stubbed in Jest config; the phantom-dep finding is a false positive — it's intentionally included even if not directly imported in source files. | ai |
Versions (showing 100 of 105)
| Version | Deps | Published |
|---|---|---|
| 3.4.69 | 7 / 17 | |
| 3.4.68 | 7 / 17 | |
| 3.4.67 | 7 / 17 | |
| 3.4.66 | 7 / 17 | |
| 3.4.65 | 7 / 17 | |
| 3.4.64 | 7 / 17 | |
| 3.4.63 | 7 / 17 | |
| 3.4.62 | 7 / 17 | |
| 3.4.61 | 7 / 17 | |
| 3.4.60 | 7 / 17 | |
| 3.4.59 | 7 / 17 | |
| 3.4.58 | 7 / 17 | |
| 3.4.57 | 7 / 17 | |
| 3.4.56 | 7 / 17 | |
| 3.4.42 | 7 / 17 | |
| 3.4.41 | 7 / 17 | |
| 3.4.40 | 7 / 17 | |
| 3.4.39 | 7 / 17 | |
| 3.4.38 | 7 / 17 | |
| 3.4.37 | 7 / 17 | |
| 3.4.36 | 7 / 17 | |
| 3.4.35 | 7 / 17 | |
| 3.4.34 | 7 / 17 | |
| 3.4.33 | 7 / 17 | |
| 3.4.32 | 7 / 17 | |
| 3.4.31 | 7 / 17 | |
| 3.4.30 | 7 / 17 | |
| 3.4.29 | 7 / 17 | |
| 3.4.28 | 7 / 17 | |
| 3.4.27 | 7 / 17 | |
| 3.4.26 | 7 / 17 | |
| 3.4.25 | 7 / 17 | |
| 3.4.24 | 7 / 17 | |
| 3.4.23 | 7 / 17 | |
| 3.4.22 | 7 / 17 | |
| 3.4.21 | 7 / 17 | |
| 3.4.20 | 7 / 17 | |
| 3.4.19 | 7 / 17 | |
| 3.4.18 | 7 / 17 | |
| 3.4.17 | 7 / 17 | |
| 3.4.16 | 7 / 17 | |
| 3.4.15 | 7 / 17 | |
| 3.4.14 | 7 / 17 | |
| 3.4.13 | 7 / 17 | |
| 3.4.12 | 7 / 17 | |
| 3.4.11 | 7 / 17 | |
| 3.4.10 | 7 / 17 | |
| 3.4.9 | 7 / 17 | |
| 3.4.8 | 7 / 17 | |
| 3.4.7 | 7 / 17 | |
| 3.4.6 | 7 / 17 | |
| 3.4.5 | 7 / 17 | |
| 3.4.4 | 7 / 17 | |
| 3.4.3 | 7 / 17 | |
| 3.4.2 | 7 / 17 | |
| 3.4.1 | 7 / 17 | |
| 3.4.0 | 7 / 17 | |
| 3.3.35 | 7 / 17 | |
| 3.3.34 | 7 / 17 | |
| 3.3.33 | 7 / 17 | |
| 3.3.32 | 7 / 17 | |
| 3.3.31 | 7 / 17 | |
| 3.3.30 | 7 / 17 | |
| 3.3.29 | 7 / 17 | |
| 3.3.28 | 7 / 17 | |
| 3.3.27 | 7 / 17 | |
| 3.3.26 | 7 / 17 | |
| 3.3.25 | 7 / 17 | |
| 3.3.24 | 7 / 17 | |
| 3.3.23 | 7 / 17 | |
| 3.3.22 | 7 / 17 | |
| 3.3.21 | 7 / 17 | |
| 3.3.20 | 7 / 17 | |
| 3.3.19 | 7 / 17 | |
| 3.3.18 | 7 / 17 | |
| 3.3.17 | 7 / 17 | |
| 3.3.16 | 7 / 17 | |
| 3.3.15 | 7 / 17 | |
| 3.3.14 | 7 / 17 | |
| 3.3.13 | 7 / 17 | |
| 3.3.12 | 7 / 17 | |
| 3.3.11 | 7 / 17 | |
| 3.3.10 | 7 / 17 | |
| 3.3.9 | 7 / 17 | |
| 3.3.8 | 7 / 17 | |
| 3.3.7 | 7 / 17 | |
| 3.3.6 | 7 / 17 | |
| 3.3.5 | 7 / 17 | |
| 3.3.4 | 7 / 17 | |
| 3.3.3 | 7 / 17 | |
| 3.3.2 | 7 / 17 | |
| 3.3.1 | 7 / 17 | |
| 3.3.0 | 7 / 17 | |
| 3.2.5 | 7 / 17 | |
| 3.2.4 | 7 / 17 | |
| 3.2.3 | 7 / 17 | |
| 3.2.2 | 7 / 17 | |
| 3.2.1 | 7 / 17 | |
| 3.2.0 | 7 / 17 | |
| 3.1.5 | 7 / 17 |
v3.4.69
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.68
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.67
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.66
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.65
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.64
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.