← Home

@pipeline-builder/event-bridge

npm Repository Homepage

AWS Lambda handler for Pipeline Builder that ingests CodePipeline state-change events from EventBridge and forwards normalized payloads to the reporting service.

38
Versions
Apache-2.0
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

mwashburn160

Keywords

awscodepipelinecodebuildcicdci-cddevopscdkaws-cdkcloudformationpipelinepipeline-as-codecontainerizeddockerkubernetespluginstypescriptself-servicemulti-tenantcomplianceautomationinfrastructure-as-codeiaccli

Versions (showing 38 of 38)

Version Deps Published
3.3.25 0 / 14
3.3.24 0 / 14
3.3.23 0 / 14
3.3.22 0 / 14
3.3.21 0 / 14
3.3.20 0 / 14
3.3.19 0 / 14
3.3.18 0 / 14
3.3.17 0 / 14
3.3.16 0 / 14
3.3.15 0 / 14
3.3.14 0 / 14
3.3.13 0 / 14
3.3.12 0 / 14
3.3.11 0 / 14
3.3.10 0 / 14
3.3.9 0 / 14
3.3.8 0 / 14
3.3.7 0 / 14
3.3.6 0 / 14
3.3.5 0 / 14
3.3.4 0 / 14
3.3.3 0 / 14
3.3.2 0 / 14
3.3.1 0 / 14
3.3.0 0 / 14
3.2.5 0 / 14
3.2.4 0 / 14
3.2.3 0 / 14
3.2.2 0 / 14
3.2.1 0 / 14
3.2.0 0 / 14
3.1.5 0 / 14
3.1.4 0 / 14
3.1.3 0 / 14
3.1.2 0 / 14
3.1.1 0 / 14
3.1.0 0 / 14

v3.2.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.2.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.2.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.2.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.2.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.