← Home

@aligent/cdk-static-hosting

npm Repository Homepage

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

33
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/csp.js AI (source-diff): Standard tsc-compiled CDK construct output; long lines are TypeScript compiler artifacts, not obfuscation. ai
source-diff obfuscated-file:lib/path-remap.js AI (source-diff): Standard tsc-compiled CDK construct output; long lines are TypeScript compiler artifacts, not obfuscation. ai
source-diff obfuscated-file:lib/static-hosting.js AI (source-diff): Standard tsc-compiled CDK construct output; long lines are TypeScript compiler artifacts, not obfuscation. ai
provenance publisher-changed AI (provenance): Transition to GitHub Actions publisher is consistent with CI/CD automation; backed by SLSA provenance attestation. ai
maintainer-change maintainer-removed AI (maintainer-change): Maintainer removal aligns with org-level CI/CD automation takeover of publishing; no malicious indicators present. ai

Versions (showing 33 of 33)

Version Deps Published
2.11.11 2 / 12
2.11.10 2 / 12
2.11.9 2 / 12
2.11.8 2 / 12
2.11.7 2 / 12
2.11.6 2 / 12
2.11.5 2 / 12
2.11.4 2 / 12
2.11.3 2 / 12
2.11.1 2 / 12
2.11.0 2 / 12
2.10.0 2 / 12
2.9.3 2 / 12
2.9.2 2 / 12
2.9.1 2 / 12
2.9.0 2 / 12
2.8.2 2 / 12
2.8.1 2 / 9
2.8.0 2 / 9
2.7.3 2 / 9
2.7.2 2 / 9
2.7.1 2 / 9
2.7.0 1 / 9
2.6.0 5 / 8
2.5.2 5 / 8
2.5.1 5 / 8
2.5.0 5 / 8
2.4.0 5 / 8
2.3.5 5 / 8
2.3.4 5 / 8
2.3.3 5 / 8
2.3.2 5 / 8
2.3.1 5 / 8

v2.11.11

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

1 finding
LOW No provenance attestation provenance

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

v2.7.1

1 finding
LOW No provenance attestation provenance

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

v2.7.0

1 finding
LOW No provenance attestation provenance

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

v2.6.0

1 finding
LOW No provenance attestation provenance

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

v2.5.2

1 finding
LOW No provenance attestation provenance

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

v2.5.1

1 finding
LOW No provenance attestation provenance

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

v2.5.0

1 finding
LOW No provenance attestation provenance

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

v2.4.0

1 finding
LOW No provenance attestation provenance

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

v2.3.5

1 finding
LOW No provenance attestation provenance

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

v2.3.4

1 finding
LOW No provenance attestation provenance

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

v2.3.3

1 finding
LOW No provenance attestation provenance

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

v2.3.2

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.

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