@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 5 of 120)
| Version | Deps | Published |
|---|---|---|
| 3.1.4 | 7 / 17 | |
| 3.1.3 | 7 / 17 | |
| 3.1.2 | 7 / 17 | |
| 3.1.1 | 7 / 17 | |
| 3.1.0 | 7 / 17 |
v3.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.2
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. Only ~12% of npm packages have provenance, so this is common but not ideal.