← Home

@aligent/cdk-waf

npm Repository Homepage

![TypeScript version](https://img.shields.io/github/package-json/dependency-version/aligent/cdk-constructs/dev/typescript?filename=packages/constructs/waf/package.json&color=red) ![AWS CDK version](https://img.shields.io/github/package-json/dependency-ver

13
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

jarrod.swiftaligent-bottom.thorogood

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:lib/waf.js AI (source-diff): File is standard tsc-compiled CDK construct output; long lines from inline JSON/rule definitions, not obfuscation. ai
provenance publisher-changed AI (provenance): Transition to GitHub Actions CI publishing with SLSA attestation; legitimate automation migration for this org. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy followed by CI/CD-automated publish with SLSA provenance; consistent with org-level tooling migration. ai
phantom-deps phantom-dep:source-map-support AI (phantom-deps): source-map-support is a declared runtime dep used via CDK/ts-node config, not direct import; stable false positive. ai

Versions (showing 13 of 13)

Version Deps Published
2.5.7 1 / 7
2.5.6 1 / 7
2.5.5 1 / 7
2.5.4 1 / 7
2.5.3 1 / 7
2.5.2 1 / 7
2.5.0 1 / 7
2.4.2 1 / 7
2.4.1 1 / 7
2.4.0 1 / 7
2.3.0 1 / 7
2.2.0 3 / 7
2.1.0 3 / 7

v2.5.7

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.3.0

1 finding
LOW No provenance attestation provenance

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

v2.2.0

1 finding
LOW No provenance attestation provenance

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

v2.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.