# Argon-app — operating profile Repository: webhostingdoo/Argon-app Source revision: Unavailable HQ revision: bc9bd4733aecd8862c6a00e7db10853d2f3fc245 Scanned: 2026-10-23T16:23:30.412Z Result: empty Static source evidence only. Runtime health, credential provisioning and current use are not verified. Secret values and raw source excerpts are excluded. ## Runtime & build No evidence found in the inspected files. This does not establish absence. To establish: Which runtime versions, build steps and operating systems are required? ## Providers & services No evidence found in the inspected files. This does not establish absence. To establish: Which provider accounts, plans and service owners are required? ## Secrets & configuration No evidence found in the inspected files. This does not establish absence. To establish: Where are these named requirements provisioned, and who owns rotation? Values are never collected. ## Schedules & background work No evidence found in the inspected files. This does not establish absence. To establish: Which declared jobs are enabled, in which environment, with what timezone and retry policy? ## APIs & webhooks No evidence found in the inspected files. This does not establish absence. To establish: Who calls each interface, with which authentication, quotas and write permissions? ## Data & storage No evidence found in the inspected files. This does not establish absence. To establish: Who owns the data, migrations, retention, backups and restoration? ## Identity & permissions No evidence found in the inspected files. This does not establish absence. To establish: Which human, service and tenant roles can read or write each resource? ## Errors & monitoring No evidence found in the inspected files. This does not establish absence. To establish: Where do errors and alerts go, who receives them, and are sensitive fields scrubbed? ## Hosting & delivery No evidence found in the inspected files. This does not establish absence. To establish: Which project/environment is deployed, and does its source match this revision? ## Devices & execution access No evidence found in the inspected files. This does not establish absence. To establish: Does operation need a browser, mobile device, local PC, filesystem or remote computer? Who grants access? ## Troubleshooting & recovery No evidence found in the inspected files. This does not establish absence. To establish: Which runbook, health checks, rollback and recovery procedure have been exercised? ## Tests & ownership No evidence found in the inspected files. This does not establish absence. To establish: Who maintains this app, what is actually in use, and which checks establish acceptance? ## Coverage and limitations 0 files inspected of 0 eligible; 0 excluded/outside scope; 0 failed reads. - Repository has no readable commit - Static inspection does not verify runtime health, current use, provisioning, live schedules, service account access or deployed/source alignment. - Only bounded source/configuration files are inspected. Secret files, data exports, binaries, history and raw source text are excluded from results. - Unknown or dynamically constructed integrations and configuration names may not be detected. Human review is still needed. - Deep scan: more source and candidate detectors, with an adjacent versioned receipt. Candidate calls and tracking matches still require interpretation.