Description
Where the ecosystem offers both, prebuilt distributions are installed instead of source distributions that execute a build script at install time. Source builds are allowed only for listed packages.
Rationale
Building from source at install time is install-time code execution, even in ecosystems that have no explicit lifecycle scripts.
Impact
Some packages only ship sources for some platforms and must be listed or built once and published to the private registry.
Audit
- Check that configuration prefers or requires prebuilt distributions.
- Review the list of packages allowed to build from source.
Automated: every check must pass. Scanners report each check by its id.
postmortem
Python: no-build / only-binary, and locked packages that ship no wheel
command: postmortem harden --json
control: CB-DEP-EXEC-002
coverage: auto
Remediation
- Require prebuilt distributions in committed configuration.
- Build the remaining packages once in a controlled pipeline and publish them to the private registry.
References
- Package Manager Best Practices OpenSSF, guide, accessed 2026-10-16
Mappings
| Framework | ID | Relation | Note |
|---|---|---|---|
| NIST SP 800-53 Rev. 55.1.1 | CM-7 | related |
How this control relates to the other framework's: equivalent, stricter, looser, partial or related.
Threats mitigated
| Taxonomy | ID | Note |
|---|---|---|
| MITRE ATT&CK | T1195.001 | |
| Common Weakness Enumeration | CWE-829 |
Related controls
- related
CB-DEP-EXEC-001Block install-time scripts except for an allowlist
People and lifecycle
| Authors | Alice |
| Introduced in | v1.0.0 |
| Created, updated | 2026-10-16, 2026-10-16 |