@cdktn/provider-github
Prebuilt github Provider for CDK Terrain (cdktn)
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:lib/actions-organization-variable-repository/index.js | AI (source-diff): Long-line jsii-generated Terraform resource class, not obfuscation. | ai | |
| source-diff | obfuscated-file:lib/data-github-release-asset/index.js | AI (source-diff): Long-line jsii-generated Terraform resource class, not obfuscation. | ai | |
| source-diff | obfuscated-file:lib/dependabot-organization-secret-repository/index.js | AI (source-diff): Long-line jsii-generated Terraform resource class, not obfuscation. | ai | |
| source-diff | obfuscated-file:lib/actions-organization-variable-repositories/index.js | AI (source-diff): Long-line jsii-generated Terraform resource class, not obfuscation. | ai | |
| source-diff | obfuscated-file:lib/actions-organization-workflow-permissions/index.js | AI (source-diff): Long-line jsii-generated Terraform resource class, not obfuscation. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Consistent with CI bot publishing transition for this generated provider package. | ai | |
| provenance | publisher-changed | AI (provenance): Manual-to-CI/CD provenance improvement, not a compromise indicator. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 17.1.0 | 0 / 18 | |
| 17.0.0 | 0 / 18 | |
| 16.1.1 | 0 / 18 | |
| 16.1.0 | 0 / 18 | |
| 16.0.0 | 0 / 18 | |
| 15.4.2 | 0 / 18 | |
| 15.4.1 | 0 / 18 | |
| 15.4.0 | 0 / 18 |
v17.1.0
2 findingsThis version was published by a different npm account than previous versions on 2026-07-09. 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.
v16.0.0
7 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.
[Accepted risk] This version was published by a different npm account than previous versions on 2026-02-18. This could indicate a legitimate maintainer transition or an account compromise.
v15.4.2
7 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.
[Accepted risk] This version was published by a different npm account than previous versions on 2026-02-12. This could indicate a legitimate maintainer transition or an account compromise.
v15.4.1
7 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.
[Accepted risk] This version was published by a different npm account than previous versions on 2026-02-08. This could indicate a legitimate maintainer transition or an account compromise.
v15.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.