@aligent/cdk-esbuild
Esbuild implementation for CDK
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 |
|---|---|---|---|---|
| provenance | slsa-provenance | AI (provenance): Package consistently published via CI with SLSA attestation; stable supply chain signal for this org. | ai | |
| phantom-deps | phantom-dep:constructs | AI (phantom-deps): constructs is a CDK peer dep referenced in config; stable false positive for CDK construct packages. | ai | |
| phantom-deps | phantom-dep:source-map-support | AI (phantom-deps): source-map-support is a runtime dep loaded implicitly; stable false positive for this package. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 2.5.10 | 4 / 7 | |
| 2.5.9 | 4 / 7 | |
| 2.5.8 | 4 / 7 | |
| 2.5.7 | 4 / 7 | |
| 2.5.6 | 4 / 7 | |
| 2.5.5 | 4 / 7 | |
| 2.5.4 | 4 / 7 | |
| 2.5.2 | 4 / 7 | |
| 2.5.1 | 4 / 7 | |
| 2.5.0 | 4 / 7 | |
| 2.4.1 | 4 / 7 | |
| 2.4.0 | 4 / 7 |
v2.5.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.5.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.5.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.5.4
2 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.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.