@aligent/cdk-shared-vpc
 : File is standard TypeScript-compiled CDK construct output; long lines are from bundled readable JS, not obfuscation. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase reflects compiled JS output from TypeScript sources; expected for CDK construct packages. | ai | |
| phantom-deps | phantom-dep:source-map-support | AI (phantom-deps): source-map-support is injected by ts-node/tsconfig at runtime, not directly imported in source files. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 0.3.8 | 1 / 7 | |
| 0.3.7 | 1 / 7 | |
| 0.3.6 | 1 / 7 | |
| 0.3.5 | 1 / 7 | |
| 0.3.4 | 1 / 7 | |
| 0.3.2 | 1 / 7 | |
| 0.3.1 | 1 / 7 | |
| 0.3.0 | 1 / 7 |
v0.3.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.4
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
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.1
2 findingsNewly 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.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.