Components with minimal dependencies
Summary
The components in the source code must have as few dependencies as possible.
Description
Having as few dependencies as possible is about being mindful of the dependencies that are introduced. It's a balance between modularity, simplicity, and flexibility that contributes to a more maintainable code over time.
Supported In
This requirement is verified in following services
| Plan | Supported |
|---|---|
| Essential | 🟢 |
| Advanced | 🟢 |
References
- NIST SSDF-PW_4_1. Reuse existing, well-secured software when feasible instead of duplicating functionality
- OWASP SAMM-SA. Security Architecture
Vulnerabilities
Free trial
Search for vulnerabilities in your apps for free with Fluid Attacks' automated security testing! Start your 21-day free trial and discover the benefits of the Continuous Hacking Essential plan. If you prefer the Advanced plan, which includes the expertise of Fluid Attacks' hacking team, fill out this contact form.