@aws-cdk/aws-logs
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/test.log-retention-provider.js | AI (source-diff): Compiled test file, not obfuscation. | ai | |
| source-diff | obfuscated-file:test/test.log-retention.js | AI (source-diff): Compiled test file, not obfuscation. | ai | |
| source-diff | obfuscated-file:lib/query-definition.js | AI (source-diff): Compiled jsii build output. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are sibling @aws-cdk packages from same trusted publisher. | ai | |
| source-diff | obfuscated-file:lib/policy.js | AI (source-diff): jsii-compiled construct source, standard for aws-cdk packages. | ai | |
| source-diff | obfuscated-file:lib/logs-canned-metrics.generated.js | AI (source-diff): Auto-generated metrics file, long lines expected. | ai | |
| npm-metadata | url-dep:cdk-build-tools | AI (npm-metadata): Internal monorepo dev tool, not a runtime dependency. | ai | |
| npm-metadata | url-dep:cdk-integ-tools | AI (npm-metadata): Internal monorepo dev tool, not a runtime dependency. | ai | |
| npm-metadata | url-dep:cfn2ts | AI (npm-metadata): Internal monorepo dev tool, not a runtime dependency. | ai | |
| npm-metadata | url-dep:pkglint | AI (npm-metadata): Internal monorepo dev tool, not a runtime dependency. | ai | |
| source-diff | obfuscated-file:lib/log-retention.js | AI (source-diff): Compiled TS output; readable CDK construct code. | ai | |
| source-diff | obfuscated-file:lib/log-retention-provider/index.js | AI (source-diff): Compiled jsii output with long lines; sample shows plain readable AWS SDK code, not obfuscation. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Expected cadence for lockstep-released official AWS CDK monorepo package. | ai | |
| source-diff | obfuscated-file-transition:test/test.metricfilter.js | AI (source-diff): Sample shows readable JS test code, not obfuscation; false positive from long lines. | ai | |
| phantom-deps | phantom-dep:constructs | AI (phantom-deps): constructs is a peer/jsii dep used indirectly; normal for CDK packages. | ai | |
| semgrep | semgrep:http-module-request | AI (semgrep): The HTTPS request in log-retention-provider/index.js is a standard CloudFormation custom resource callback pattern — not telemetry or exfiltration. Stable for this package. | ai | |
| phantom-deps | phantom-dep:@aws-cdk/cx-api | AI (phantom-deps): @aws-cdk/cx-api is explicitly declared in both dependencies and peerDependencies in package.json; phantom-dep finding is a false positive for this package. | ai |
Versions (showing 42 of 242)
| Version | Deps | Published |
|---|---|---|
| 1.32.1 | 4 / 7 | |
| 1.32.0 | 4 / 7 | |
| 1.31.0 | 4 / 7 | |
| 1.30.0 | 4 / 7 | |
| 1.29.0 | 4 / 7 | |
| 1.28.0 | 3 / 7 | |
| 1.27.0 | 3 / 7 | |
| 1.26.0 | 3 / 7 | |
| 1.25.0 | 3 / 7 | |
| 1.24.0 | 3 / 7 | |
| 1.23.0 | 3 / 7 | |
| 1.22.0 | 3 / 7 | |
| 1.21.1 | 3 / 7 | |
| 1.21.0 | 3 / 7 | |
| 1.20.0 | 3 / 7 | |
| 1.19.0 | 3 / 5 | |
| 1.18.0 | 3 / 5 | |
| 1.17.1 | 3 / 5 | |
| 1.17.0 | 3 / 5 | |
| 1.16.3 | 3 / 5 | |
| 1.16.2 | 3 / 5 | |
| 1.16.1 | 3 / 5 | |
| 1.16.0 | 3 / 5 | |
| 1.15.0 | 3 / 5 | |
| 1.14.0 | 3 / 5 | |
| 1.13.1 | 3 / 5 | |
| 1.13.0 | 3 / 5 | |
| 1.12.0 | 3 / 5 | |
| 1.11.0 | 3 / 5 | |
| 1.10.1 | 3 / 5 | |
| 1.10.0 | 3 / 5 | |
| 1.9.0 | 3 / 5 | |
| 1.8.0 | 3 / 5 | |
| 1.7.0 | 3 / 5 | |
| 1.6.1 | 3 / 5 | |
| 1.6.0 | 3 / 5 | |
| 1.5.0 | 3 / 5 | |
| 1.4.0 | 3 / 5 | |
| 1.3.0 | 3 / 5 | |
| 1.2.0 | 3 / 5 | |
| 1.1.0 | 3 / 5 | |
| 1.0.0 | 3 / 5 |
v1.32.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.21.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.