# Pitfall Log / 踩坑日志

项目：bridgecrewio/checkov

摘要：发现 35 个潜在踩坑项，其中 9 个为 high/blocking；最高优先级：安装坑 - 来源证据：Bicep / ARM support expectations are misleading for real-world Azure usage。

## 1. 安装坑 · 来源证据：Bicep / ARM support expectations are misleading for real-world Azure usage

- 严重度：high
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安装相关的待验证问题：Bicep / ARM support expectations are misleading for real-world Azure usage
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/bridgecrewio/checkov/issues/7394 | 来源类型 github_issue 暴露的待验证使用条件。

## 2. 安装坑 · 来源证据：Discrepancy Between Homebrew vs pip Installations: CKV2 Checks Not Running with Homebrew

- 严重度：high
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安装相关的待验证问题：Discrepancy Between Homebrew vs pip Installations: CKV2 Checks Not Running with Homebrew
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/bridgecrewio/checkov/issues/6645 | 来源讨论提到 python 相关条件，需在安装/试用前复核。

## 3. 安装坑 · 来源证据：update Python module packaging

- 严重度：high
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安装相关的待验证问题：update Python module packaging
- 对用户的影响：可能阻塞安装或首次运行。
- 证据：community_evidence:github | https://github.com/bridgecrewio/checkov/issues/6950 | 来源讨论提到 python 相关条件，需在安装/试用前复核。

## 4. 配置坑 · 来源证据：GCS Bucket Logging Checks with Undetermined Value

- 严重度：high
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个配置相关的待验证问题：GCS Bucket Logging Checks with Undetermined Value
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/bridgecrewio/checkov/issues/7473 | 来源类型 github_issue 暴露的待验证使用条件。

## 5. 安全/权限坑 · 失败模式：security_permissions: Security: Multiple CVEs in Dependencies (urllib3, asteval, ply) - Checkov 3.2.517

- 严重度：high
- 证据强度：source_linked
- 发现：Developers should check this security_permissions risk before relying on the project: Security: Multiple CVEs in Dependencies (urllib3, asteval, ply) - Checkov 3.2.517
- 对用户的影响：Developers may expose sensitive permissions or credentials: Security: Multiple CVEs in Dependencies (urllib3, asteval, ply) - Checkov 3.2.517
- 证据：failure_mode_cluster:github_issue | https://github.com/bridgecrewio/checkov/issues/7504 | Security: Multiple CVEs in Dependencies (urllib3, asteval, ply) - Checkov 3.2.517

## 6. 安全/权限坑 · 来源证据：CKV_GCP_93 false positive when using multi-key configuration

- 严重度：high
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安全/权限相关的待验证问题：CKV_GCP_93 false positive when using multi-key configuration
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/bridgecrewio/checkov/issues/7402 | 来源类型 github_issue 暴露的待验证使用条件。

## 7. 安全/权限坑 · 来源证据：Expose variables from terraform plan

- 严重度：high
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安全/权限相关的待验证问题：Expose variables from terraform plan
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/bridgecrewio/checkov/issues/7396 | 来源类型 github_issue 暴露的待验证使用条件。

## 8. 安全/权限坑 · 来源证据：Kubernetes manifests with ${VAR} placeholders are silently skipped

- 严重度：high
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安全/权限相关的待验证问题：Kubernetes manifests with ${VAR} placeholders are silently skipped
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/bridgecrewio/checkov/issues/7210 | 来源类型 github_issue 暴露的待验证使用条件。

## 9. 安全/权限坑 · 来源证据：Security: Multiple CVEs in Dependencies (urllib3, asteval, ply) - Checkov 3.2.517

- 严重度：high
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安全/权限相关的待验证问题：Security: Multiple CVEs in Dependencies (urllib3, asteval, ply) - Checkov 3.2.517
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/bridgecrewio/checkov/issues/7504 | 来源讨论提到 python 相关条件，需在安装/试用前复核。

## 10. 安装坑 · 失败模式：installation: Discrepancy Between Homebrew vs pip Installations: CKV2 Checks Not Running with Homebrew

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this installation risk before relying on the project: Discrepancy Between Homebrew vs pip Installations: CKV2 Checks Not Running with Homebrew
- 对用户的影响：Developers may fail before the first successful local run: Discrepancy Between Homebrew vs pip Installations: CKV2 Checks Not Running with Homebrew
- 证据：failure_mode_cluster:github_issue | https://github.com/bridgecrewio/checkov/issues/6645 | Discrepancy Between Homebrew vs pip Installations: CKV2 Checks Not Running with Homebrew

## 11. 安装坑 · 失败模式：installation: feat(general): Add warnings when API-dependent parameters are used without API key

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this installation risk before relying on the project: feat(general): Add warnings when API-dependent parameters are used without API key
- 对用户的影响：Developers may fail before the first successful local run: feat(general): Add warnings when API-dependent parameters are used without API key
- 证据：failure_mode_cluster:github_issue | https://github.com/bridgecrewio/checkov/issues/7379 | feat(general): Add warnings when API-dependent parameters are used without API key

## 12. 安装坑 · 失败模式：installation: update Python module packaging

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this installation risk before relying on the project: update Python module packaging
- 对用户的影响：Developers may fail before the first successful local run: update Python module packaging
- 证据：failure_mode_cluster:github_issue | https://github.com/bridgecrewio/checkov/issues/6950 | update Python module packaging

## 13. 配置坑 · 失败模式：configuration: Bicep: Missing parser support for `extension` keyword

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this configuration risk before relying on the project: Bicep: Missing parser support for `extension` keyword
- 对用户的影响：Developers may misconfigure credentials, environment, or host setup: Bicep: Missing parser support for `extension` keyword
- 证据：failure_mode_cluster:github_issue | https://github.com/bridgecrewio/checkov/issues/7364 | Bicep: Missing parser support for `extension` keyword

## 14. 配置坑 · 失败模式：configuration: CKV_AWS_86 only validates v1 logging, not v2

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this configuration risk before relying on the project: CKV_AWS_86 only validates v1 logging, not v2
- 对用户的影响：Developers may misconfigure credentials, environment, or host setup: CKV_AWS_86 only validates v1 logging, not v2
- 证据：failure_mode_cluster:github_issue | https://github.com/bridgecrewio/checkov/issues/7385 | CKV_AWS_86 only validates v1 logging, not v2

## 15. 配置坑 · 失败模式：configuration: CKV_GCP_123 triggers even if remove_default_node_pool is set

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this configuration risk before relying on the project: CKV_GCP_123 triggers even if remove_default_node_pool is set
- 对用户的影响：Developers may misconfigure credentials, environment, or host setup: CKV_GCP_123 triggers even if remove_default_node_pool is set
- 证据：failure_mode_cluster:github_issue | https://github.com/bridgecrewio/checkov/issues/7406 | CKV_GCP_123 triggers even if remove_default_node_pool is set

## 16. 配置坑 · 失败模式：configuration: CKV_GCP_93 false positive when using multi-key configuration

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this configuration risk before relying on the project: CKV_GCP_93 false positive when using multi-key configuration
- 对用户的影响：Developers may misconfigure credentials, environment, or host setup: CKV_GCP_93 false positive when using multi-key configuration
- 证据：failure_mode_cluster:github_issue | https://github.com/bridgecrewio/checkov/issues/7402 | CKV_GCP_93 false positive when using multi-key configuration

## 17. 配置坑 · 失败模式：configuration: GCS Bucket Logging Checks with Undetermined Value

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this configuration risk before relying on the project: GCS Bucket Logging Checks with Undetermined Value
- 对用户的影响：Developers may misconfigure credentials, environment, or host setup: GCS Bucket Logging Checks with Undetermined Value
- 证据：failure_mode_cluster:github_issue | https://github.com/bridgecrewio/checkov/issues/7473 | GCS Bucket Logging Checks with Undetermined Value

## 18. 配置坑 · 来源证据：CKV_GCP_123 triggers even if remove_default_node_pool is set

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个配置相关的待验证问题：CKV_GCP_123 triggers even if remove_default_node_pool is set
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/bridgecrewio/checkov/issues/7406 | 来源讨论提到 node 相关条件，需在安装/试用前复核。

## 19. 能力坑 · 能力判断依赖假设

- 严重度：medium
- 证据强度：source_linked
- 发现：README/documentation is current enough for a first validation pass.
- 对用户的影响：假设不成立时，用户拿不到承诺的能力。
- 证据：capability.assumptions | https://github.com/bridgecrewio/checkov | README/documentation is current enough for a first validation pass.

## 20. 运行坑 · 运行可能依赖外部服务

- 严重度：medium
- 证据强度：source_linked
- 发现：项目说明出现 external service/cloud/webhook/database 等运行依赖关键词。
- 对用户的影响：本地安装成功不等于能力可用，外部服务不可用会阻断体验。
- 证据：packet_text.keyword_scan | https://github.com/bridgecrewio/checkov | matched external service / cloud / webhook / database keyword

## 21. 维护坑 · 维护活跃度未知

- 严重度：medium
- 证据强度：source_linked
- 发现：未记录 last_activity_observed。
- 对用户的影响：新项目、停更项目和活跃项目会被混在一起，推荐信任度下降。
- 证据：evidence.maintainer_signals | https://github.com/bridgecrewio/checkov | last_activity_observed missing

- 严重度：medium
- 证据强度：source_linked
- 发现：no_demo
- 证据：downstream_validation.risk_items | https://github.com/bridgecrewio/checkov | no_demo; severity=medium

## 23. 安全/权限坑 · 存在评分风险

- 严重度：medium
- 证据强度：source_linked
- 发现：no_demo
- 对用户的影响：风险会影响是否适合普通用户安装。
- 证据：risks.scoring_risks | https://github.com/bridgecrewio/checkov | no_demo; severity=medium

## 24. 安全/权限坑 · 来源证据：Bicep: Missing parser support for `extension` keyword

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安全/权限相关的待验证问题：Bicep: Missing parser support for `extension` keyword
- 对用户的影响：可能影响授权、密钥配置或安全边界。
- 证据：community_evidence:github | https://github.com/bridgecrewio/checkov/issues/7364 | 来源讨论提到 python 相关条件，需在安装/试用前复核。

## 25. 安全/权限坑 · 来源证据：CKV_AWS_86 only validates v1 logging, not v2

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安全/权限相关的待验证问题：CKV_AWS_86 only validates v1 logging, not v2
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/bridgecrewio/checkov/issues/7385 | 来源讨论提到 docker 相关条件，需在安装/试用前复核。

## 26. 安全/权限坑 · 来源证据：feat(general): Add warnings when API-dependent parameters are used without API key

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安全/权限相关的待验证问题：feat(general): Add warnings when API-dependent parameters are used without API key
- 对用户的影响：可能影响授权、密钥配置或安全边界。
- 证据：community_evidence:github | https://github.com/bridgecrewio/checkov/issues/7379 | 来源讨论提到 python 相关条件，需在安装/试用前复核。

## 27. 能力坑 · 失败模式：capability: Bicep / ARM support expectations are misleading for real-world Azure usage

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this capability risk before relying on the project: Bicep / ARM support expectations are misleading for real-world Azure usage
- 对用户的影响：Developers may hit a documented source-backed failure mode: Bicep / ARM support expectations are misleading for real-world Azure usage
- 证据：failure_mode_cluster:github_issue | https://github.com/bridgecrewio/checkov/issues/7394 | Bicep / ARM support expectations are misleading for real-world Azure usage

## 28. 能力坑 · 失败模式：capability: Expose variables from terraform plan

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this capability risk before relying on the project: Expose variables from terraform plan
- 对用户的影响：Developers may hit a documented source-backed failure mode: Expose variables from terraform plan
- 证据：failure_mode_cluster:github_issue | https://github.com/bridgecrewio/checkov/issues/7396 | Expose variables from terraform plan

## 29. 能力坑 · 失败模式：capability: Kubernetes manifests with ${VAR} placeholders are silently skipped

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this capability risk before relying on the project: Kubernetes manifests with ${VAR} placeholders are silently skipped
- 对用户的影响：Developers may hit a documented source-backed failure mode: Kubernetes manifests with ${VAR} placeholders are silently skipped
- 证据：failure_mode_cluster:github_issue | https://github.com/bridgecrewio/checkov/issues/7210 | Kubernetes manifests with ${VAR} placeholders are silently skipped

## 30. 维护坑 · issue/PR 响应质量未知

- 严重度：low
- 证据强度：source_linked
- 发现：issue_or_pr_quality=unknown。
- 对用户的影响：用户无法判断遇到问题后是否有人维护。
- 证据：evidence.maintainer_signals | https://github.com/bridgecrewio/checkov | issue_or_pr_quality=unknown

## 31. 维护坑 · 发布节奏不明确

- 严重度：low
- 证据强度：source_linked
- 发现：release_recency=unknown。
- 对用户的影响：安装命令和文档可能落后于代码，用户踩坑概率升高。
- 证据：evidence.maintainer_signals | https://github.com/bridgecrewio/checkov | release_recency=unknown

## 32. 维护坑 · 失败模式：maintenance: 3.2.533

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this maintenance risk before relying on the project: 3.2.533
- 对用户的影响：Upgrade or migration may change expected behavior: 3.2.533
- 证据：failure_mode_cluster:github_release | https://github.com/bridgecrewio/checkov/releases/tag/3.2.533 | 3.2.533

## 33. 维护坑 · 失败模式：maintenance: 3.2.534

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this maintenance risk before relying on the project: 3.2.534
- 对用户的影响：Upgrade or migration may change expected behavior: 3.2.534
- 证据：failure_mode_cluster:github_release | https://github.com/bridgecrewio/checkov/releases/tag/3.2.534 | 3.2.534

## 34. 维护坑 · 失败模式：maintenance: 3.3.0

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this maintenance risk before relying on the project: 3.3.0
- 对用户的影响：Upgrade or migration may change expected behavior: 3.3.0
- 证据：failure_mode_cluster:github_release | https://github.com/bridgecrewio/checkov/releases/tag/3.3.0 | 3.3.0

## 35. 维护坑 · 失败模式：maintenance: 3.3.1

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this maintenance risk before relying on the project: 3.3.1
- 对用户的影响：Upgrade or migration may change expected behavior: 3.3.1
- 证据：failure_mode_cluster:github_release | https://github.com/bridgecrewio/checkov/releases/tag/3.3.1 | 3.3.1