@cdktn/provider-schema
CDK Terrain utilities to work with provider schemas
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Consistent across all versions of this package; publisher has strong approval track record. | ai | |
| source-diff | obfuscated-file:build/cache.js | AI (source-diff): TypeScript tsc output with long lines from generated boilerplate; not obfuscated. | ai | |
| source-diff | obfuscated-file:build/provider-schema.js | AI (source-diff): TypeScript tsc output; readable HashiCorp-licensed source, not obfuscated. | ai | |
| source-diff | obfuscated-file:build/__tests__/provider-schema.test.js | AI (source-diff): TypeScript tsc output of test file; not obfuscated. | ai | |
| source-diff | obfuscated-file:build/read.js | AI (source-diff): TypeScript tsc output; readable source, not obfuscated. | ai | |
| source-diff | obfuscated-file:build/util.js | AI (source-diff): TypeScript tsc output; readable source, not obfuscated. | ai | |
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI publisher with SLSA attestation is expected for this org. | ai | |
| source-diff | obfuscated-file:build/__tests__/provider-schema.unit.test.js | AI (source-diff): TypeScript tsc output of unit test file; not obfuscated. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): CDK/Terraform tooling package; child_process used for legitimate exec utilities, stable pattern across versions. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.23.3 | 4 / 4 | |
| 0.23.2 | 4 / 5 | |
| 0.23.1 | 4 / 7 | |
| 0.23.0 | 4 / 7 | |
| 0.22.1 | 4 / 18 | |
| 0.22.0 | 4 / 18 | |
| 0.21.0 | 4 / 18 |
v0.23.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.23.2
8 findingsThis 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.
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.
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.23.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.