← Home

@liflig/cdk-cloudfront-auth

npm Repository Homepage

CDK Constructs for adding authentication for a CloudFront Distribution

100
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

capra-cijol-capraconsultingevan-boonesondrehavsba.capraconsulting

Keywords

cdkcloudfrontauthentication

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition from capra-ci to GitHub Actions CI/CD with SLSA provenance attestation; legitimate pipeline migration. ai
semgrep semgrep:base64-decode AI (semgrep): Base64 decoding is a core, expected operation in this OAuth/JWT authentication library for handling URL-safe base64 tokens. Not a malicious payload indicator. ai

Versions (showing 100 of 291)

Version Deps Published
1.10.12 0 / 22
1.10.11 0 / 22
1.10.10 0 / 22
1.10.9 0 / 22
1.10.8 0 / 22
1.10.7 0 / 22
1.10.6 0 / 22
1.10.5 0 / 22
1.10.4 0 / 22
1.10.3 0 / 22
1.10.2 0 / 22
1.10.1 0 / 22
1.10.0 0 / 22
1.9.2 2 / 20
1.9.1 2 / 20
1.9.0 2 / 20
1.8.41 2 / 26
1.8.40 2 / 26
1.8.39 2 / 26
1.8.38 2 / 26
1.8.37 2 / 26
1.8.36 2 / 26
1.8.35 2 / 26
1.8.34 2 / 26
1.8.33 2 / 26
1.8.32 2 / 26
1.8.31 2 / 26
1.8.30 2 / 26
1.8.29 2 / 26
1.8.28 2 / 26
1.8.27 2 / 26
1.8.26 2 / 26
1.8.25 2 / 26
1.8.24 2 / 26
1.8.23 2 / 26
1.8.22 2 / 26
1.8.21 2 / 26
1.8.20 2 / 26
1.8.19 2 / 26
1.8.18 2 / 26
1.8.17 2 / 26
1.8.16 2 / 26
1.8.15 2 / 26
1.8.14 2 / 26
1.8.13 2 / 26
1.8.12 2 / 26
1.8.11 2 / 26
1.8.10 2 / 26
1.8.9 2 / 26
1.8.8 2 / 26
1.8.7 2 / 26
1.8.6 2 / 26
1.8.5 2 / 26
1.8.4 2 / 26
1.8.3 2 / 26
1.8.2 2 / 26
1.8.1 2 / 26
1.8.0 2 / 26
1.7.20 2 / 25
1.7.19 2 / 25
1.7.18 2 / 25
1.7.17 2 / 25
1.7.16 2 / 25
1.7.15 2 / 25
1.7.14 2 / 25
1.7.13 2 / 25
1.7.12 2 / 25
1.7.11 2 / 25
1.7.10 2 / 25
1.7.9 2 / 25
1.7.8 2 / 25
1.7.7 2 / 25
1.7.6 2 / 25
1.7.5 2 / 25
1.7.4 2 / 25
1.7.3 2 / 25
1.7.2 2 / 25
1.7.1 2 / 25
1.7.0 2 / 25
1.6.136 2 / 32
1.6.135 2 / 32
1.6.134 2 / 32
1.6.133 2 / 32
1.6.132 2 / 32
1.6.131 2 / 32
1.6.130 2 / 32
1.6.129 2 / 32
1.6.128 2 / 32
1.6.127 2 / 32
1.6.126 2 / 32
1.6.125 2 / 32
1.6.124 2 / 32
1.6.123 2 / 32
1.6.122 2 / 32
1.6.121 2 / 32
1.6.120 2 / 32
1.6.119 2 / 32
1.6.118 2 / 32
1.6.117 2 / 32
1.6.116 2 / 32
Showing 100 of 291 Next page →

v1.10.12

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.

v1.10.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.

v1.6.124

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.

v1.6.123

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.

v1.6.122

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.

v1.6.121

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.

v1.6.120

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.

v1.6.119

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.

v1.6.118

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.

v1.6.117

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.

v1.6.116

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.