Assess whether source code is ready to deploy to Azure — the check BEFORE infrastructure work. Evaluates build health, app completeness, dependencies and local services, stack compatibility, and deployment feasibility. Answers questions about what your app needs before it can be deployed — frameworks, dependencies, and configuration. Checks whether dependencies are compatible and identifies deployment blockers and unsupported frameworks. WHEN: "evaluate my repo", "is my app ready to deploy", "what does my app need to deploy", "what do I need before deploying", "does my app need", "can I ship this to Azure", "scan my repo for issues", "is this app deployable", "check if my app is ready for Azure", "do I need a Dockerfile", "what's blocking my deployment", "are there any blockers", "are my dependencies compatible", "does Azure support my framework", "what needs to change before deploying", "check my app configuration".
◌Internal reference resolution completednothing foundAll body-referenced paths under references/, scripts/, and assets/ resolved in the bundle.vettd · scan · 2wnothing found
Not assessed; no producer has emitted into cost for this asset. That is different from a check that ran and found nothing, which the record would carry as a row of its own.
assessed2w ago · Cisco AI Defense · Vettd core● current
source stateThe source matches what was scanned. No changes detected.Up to date
re-check policyre-checked against the upstream source on the scheduler's cadencenext check in 15h
re-run whena new release ships, the upstream source changes, or the scanner ruleset is revisedauto-scheduled
Limitations & open conflicts
limitationCost is not assessed: behaviour there is unmeasured, not clean△ gap
limitationSafety, Reliability & Quality carries rows but no severity-bearing one: nothing has been graded there△ gap
conflictno two sources report the same quantity on this record
Verify: does this record describe your copy?
What record 48b65649-f27a-4b01-b0ff-d185dc2229c1 covers
scannerv11● current
validityassessed 2w ago · Up to date
$vettd scan folder <path>
this record was taken at digest sha256:da6314ba0483… compare it against the digest your own scan prints
Reproduce: re-run the evidence yourself
$vettd scan folder /path/to/your/copy
runs the same scanners against your own copy; the published record is never overwritten
How this record comparesagainst other published records · full comparison →
Signal kinds
▲ finding: something to act on, carries a severity● measurement: a reproducible quantityƒ estimate: inferred from a sample▪ fact: read directly off the artifact◆ classification: assigned from a taxonomy◌ nothing found: a producer looked and emitted no object◇ context only: described, never graded
Custody marks
◐ computed by vettd○ declared by the publisher, as-is△ not assessed: nothing looked
Weigh azure-app-onboard-prereq against other published skills: the safety grade, its finding counts and each category’s verdict, one row apiece. The full comparison page carries every signal and framework coverage.