EA Dependency Scanner
Review supported references before changing an extension attribute.
The EA Dependency Scanner answers a narrow but high-value question: where is this extension attribute referenced across the Jamf surfaces Veridominus can inspect with real evidence.
Evidence lanesCoverage rowsConservative cleanup handling
Evidence lanes
- Confirmed Reference
- Confirmed Literal Script Reference
- Unsupported Exact Reference
- Review Required
These lanes exist so the scanner can preserve real evidence without pretending every hit has the same certainty or supported relationship model.
Coverage model
Each scan shows what was checked, what completed, what remained partial, and which surfaces are unsupported. Unsupported or incomplete coverage must not be read as no references found.
Conservative by design
If unsupported exact references, review-required signals, or incomplete supported coverage are present, the scanner does not present the extension attribute as confidently unused.
Supported domains in the current release
- Jamf dependency API, where the endpoint returns supported dependent objects
- Smart group criteria
- Advanced search criteria and display columns
- Managed App Configuration variable references, where the payload exposes exact EA variables
- Strict literal script references for the supported script-analysis patterns
What the scanner does not claim
- It is not a universal script-analysis engine.
- It does not treat unsupported exact references as supported confirmed references.
- It does not prove absence when supported checks are partial or unsupported.