← Home

@cdktn/commons

npm Repository Homepage

CDK Terrain Common utilities

6
Versions
MPL-2.0
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

cdktn-teamjsteinichso0k

Keywords

cdkcdktfcdktnterraform

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Package migrated to GitHub Actions CI publishing with SLSA attestation; this is the expected pattern for this org. ai
maintainer-change maintainer-added AI (maintainer-change): jsteinich is a known contributor in the open-constructs org; addition consistent with legitimate team expansion. ai
semgrep semgrep:env-spread AI (semgrep): env-spread is used to pass process.env to a child process exec call — standard pattern, not exfiltration. ai
semgrep semgrep:dynamic-require AI (semgrep): Dynamic require loads a resolved JSON file path, not arbitrary user input; stable false positive for this package. ai

Versions (showing 6 of 6)

Version Deps Published
0.23.2 11 / 6
0.23.1 11 / 8
0.23.0 11 / 8
0.22.1 11 / 17
0.22.0 11 / 17
0.21.0 11 / 17

v0.23.2

2 findings
HIGH Publisher changed: cdktn-team → GitHub Actions (on 2026-05-26) provenance

This version was published by a different npm account than previous versions on 2026-05-26. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.23.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.23.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.22.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.21.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.