mutants/src: pre-commit_+_ci_hardening
| *Community 18 |
3 files |
cohesion 1.00* |
Definition
This community groups 3 file(s) rooted at mutants/src with dominant language c (cohesion 1.00). Central symbols: PRE. Core file: include/pre-commit_+_ci_hardening.h (1 symbols). Documented purpose: Auto-generated implementation for contract: Pre-commit + CI Hardening.
Files
| File |
Language |
Layer |
Symbols |
Doc |
include/pre-commit_+_ci_hardening.h |
h |
utility |
1 |
no |
mutants/src/pre-commit_+_ci_hardening.c |
c |
utility |
0 |
yes |
src/pre-commit_+_ci_hardening.c |
c |
utility |
0 |
yes |
Key Symbols
PRE (macro, include/pre-commit_+_ci_hardening.h:2) #define PRE
Internal vs External Edges
- Internal resolved imports (EXTRACTED): 2
- Cross-boundary resolved imports (EXTRACTED): 0
Connections
- [INFERRED] shares_context community 0 <-> 18 (strength 0.5): Inferred shared context (language c and layer utility) with no import path between community 0 (legacy) and community 18 (mutants/src: pre-commit_+_ci_hardening).
Risks
- No scoped security, taint, cycle, or layer risks.
Open Questions
- Why do 1 file(s) lack file-level docs (e.g.
include/pre-commit_+_ci_hardening.h)? What purpose do they serve?
- What would break if the most connected file in mutants/src: pre-commit_+_ci_hardening changed?
- Should mutants/src: pre-commit_+_ci_hardening be split, given cohesion 1.00?
Sources
include/pre-commit_+_ci_hardening.h
mutants/src/pre-commit_+_ci_hardening.c
src/pre-commit_+_ci_hardening.c