Why this matters: erpweb_phase3_risky_test_module is currently rated CRITICAL with score 299. 1 high scanner finding(s) found. 5 medium scanner finding(s) found.
Recommended action: Start with this module first. Resolve blockers, critical/high findings, and retest before moving to lower-risk modules.
File: erpweb_phase3_risky_test_module/models/risky_model.py:10
Why this matters: This file appears to use the old cr, uid, ids, context method signature.
Recommended action: Convert old API methods to modern Odoo environment API using self.env and recordsets.
File: erpweb_phase3_risky_test_module/static/src/js/risky.js:1
Recommended action: Review whether this should be converted to the modern Odoo JavaScript module format.
File: erpweb_phase3_risky_test_module/static/src/js/risky.js:3
Recommended action: Review frontend imports and services against the target Odoo version.
File: erpweb_phase3_risky_test_module/models/risky_model.py:6
Recommended action: Review and convert the method to modern recordset-style API for the target Odoo version.
File: erpweb_phase3_risky_test_module/views/risky_views.xml:5
Recommended action: Review state-based visibility/read-only logic for compatibility with the target Odoo version.
File: erpweb_phase3_risky_test_module/views/risky_views.xml:5
Recommended action: Review this view against the target Odoo version's XML/view modifier requirements.
Recommended action: Confirm whether the manifest version is correct for the source branch being upgraded.
Recommended action: In the dependency graph phase, split and validate these dependencies against target Odoo version availability.
Recommended action: Review the dependency summary report for missing custom dependencies before starting code migration.
Recommended action: Later phases should validate these dependencies against the target Odoo version and installed app set.
Recommended action: Later phases should validate these dependencies against target Odoo version and installed app set.
Recommended action: In the real scanner phase, parse this manifest and validate depends, assets, license and version format.
Recommended action: Continue with dependency and code-pattern scanning.
Recommended action: Continue with dependency and code-pattern scanning.
Recommended order: fix blockers first, then critical items, then high-risk modules, then medium/low findings.
Developer handover: open Work Packages for task breakdown, estimates, and acceptance criteria.
After fixes: re-upload updated module ZIPs, run Extract & Parse ZIP again, rebuild dependencies, rebuild risk scores, and refresh this page.
This page is advisory only. It does not modify module code, run migrations, or perform any upgrade automatically.