@aws-solutions-constructs/aws-cloudfront-s3
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:test/cloudfront-s3.test.js | AI (source-diff): Compiled test file with long lines; content is plain AWS-licensed test code, not obfuscation. | ai | |
| dependencies | unvetted-dep:@aws-solutions-constructs/resources | AI (dependencies): First-party sibling package from same AWS monorepo/publisher. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Normal release cadence for this long-running AWS construct package. | ai | |
| provenance | no-provenance | AI (provenance): AWS Solutions Constructs packages consistently lack Sigstore provenance; stable false positive for this package family. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 2.102.0 | 3 / 4 | |
| 2.101.0 | 3 / 4 | |
| 2.100.1 | 3 / 4 | |
| 2.100.0 | 3 / 4 | |
| 2.99.0 | 3 / 4 | |
| 2.98.0 | 3 / 4 | |
| 2.93.0 | 3 / 4 | |
| 2.92.2 | 3 / 4 | |
| 2.92.1 | 3 / 4 | |
| 2.92.0 | 3 / 4 | |
| 2.91.0 | 3 / 4 | |
| 2.90.4 | 3 / 4 | |
| 2.90.3 | 3 / 4 | |
| 2.90.2 | 3 / 4 | |
| 2.90.1 | 3 / 4 | |
| 2.90.0 | 3 / 4 | |
| 2.87.0 | 3 / 4 | |
| 2.86.0 | 3 / 4 | |
| 2.85.6 | 3 / 4 | |
| 2.79.1 | 3 / 4 | |
| 2.79.0 | 3 / 4 | |
| 2.78.1 | 3 / 4 | |
| 2.78.0 | 3 / 4 | |
| 2.77.0 | 3 / 4 | |
| 2.76.0 | 3 / 4 | |
| 2.75.0 | 3 / 4 |
v2.101.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.100.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.100.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.99.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.93.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.92.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.92.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.92.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.91.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.90.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.90.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.90.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.90.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.90.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.87.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.86.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.85.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.79.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.79.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.78.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.78.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.77.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.76.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.75.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.