bee:pre-dev-dependency-map

Enforce explicit versioning by validating and documenting specific package versions against organizational standards. This prevents vague technology selections and mitigates security vulnerabilities by ensuring reproducible builds and compatibility across all project components.

Ensure license compliance and security by scanning dependencies for vulnerabilities (CVEs) and verifying commercial license adherence. This validates that selected backend, frontend, and infrastructure components meet organizational guidelines before development begins.

Generate project rules by integrating TRD technology decisions with Bee Standards to produce a PROJECT_RULES.md file. This documents explicit, versioned technology choices, enforcing standards compliance and justifying selections for comprehensive project governance.

Lock down technology choices before starting development on new features to avoid hidden incompatibilities and mitigate security risks. This ensures chosen databases, frameworks, and libraries are explicitly defined, checked for vulnerabilities, and approved according to guidelines.

Yes, dependency mapping applies to backend, frontend, and infrastructure components. It validates technology choices against Bee Standards, ensuring compatibility, license adherence, and cost analysis across the entire software project stack.

Unverified technology dependencies cause reproducibility issues because they lack explicit versioning and standards validation. This leads to hidden incompatibilities and security risks from unscanned vulnerabilities, preventing consistent builds across environments.