@aligent/cdk-aspects
Collection of CDK Asppects
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:lib/lambda-sfn-versioning.js | AI (source-diff): Readable TypeScript-compiled JS with JSDoc; long lines are from tsc output, not obfuscation. | ai | |
| source-diff | obfuscated-file:lib/defaults/log-group.js | AI (source-diff): Readable TypeScript-compiled JS with JSDoc; long lines are from tsc output, not obfuscation. | ai | |
| source-diff | obfuscated-file:lib/microservice-checks.js | AI (source-diff): Readable TypeScript-compiled JS with JSDoc; long lines are from tsc output, not obfuscation. | ai | |
| source-diff | obfuscated-file:lib/defaults/nodejs-function.js | AI (source-diff): Readable TypeScript-compiled JS with JSDoc; long lines are from tsc output, not obfuscation. | ai | |
| source-diff | obfuscated-file:lib/defaults/step-functions.js | AI (source-diff): Readable TypeScript-compiled JS with JSDoc; long lines are from tsc output, not obfuscation. | ai | |
| phantom-deps | phantom-dep:esbuild | AI (phantom-deps): esbuild is a known implicit dep for NodejsFunction bundling in CDK; not directly imported in library code. | ai | |
| phantom-deps | phantom-dep:source-map-support | AI (phantom-deps): source-map-support is injected at runtime by ts-node/jest config, not directly imported. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 0.6.3 | 4 / 7 | |
| 0.6.2 | 4 / 7 | |
| 0.6.1 | 4 / 7 | |
| 0.5.7 | 4 / 7 | |
| 0.5.6 | 4 / 7 | |
| 0.5.5 | 4 / 7 | |
| 0.5.3 | 4 / 7 | |
| 0.5.2 | 4 / 7 | |
| 0.5.1 | 4 / 7 | |
| 0.3.2 | 4 / 7 | |
| 0.3.0 | 4 / 7 | |
| 0.2.0 | 4 / 7 |
v0.6.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.2
7 findingsThis version was published by a different npm account than previous versions on 2026-02-11. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.0
6 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.