Development preview / synthetic data
The report is public.
The decision is yours.
A source can name an affected release. Your workspace needs to know what is deployed, which conditions apply, who owns the response, and what evidence would close the loop.
This demonstration is synthetic. It has not inspected a repository, host or customer environment. It is not a deployable integration or a purchased entitlement.
One issue, followed through.
A declared version is a starting point.
Example workload A declares PHP 8.2.18. The deployed build and CGI configuration are still unknown.
Evidence: declared · Freshness: demonstration only
Missing conditions remain unknown.
The synthetic example matches a historical PHP version boundary, but Windows, CGI and codepage facts still need evidence. The preliminary result remains potentially affected.
No exposure or compromise has been established.
Give the next check an owner.
The example service team owns the deployment check. The plan is to confirm the runtime, select a currently supported compatible target, and record the deployment evidence.
No code change or remediation runs automatically.
A source-listed fix cannot close the finding.
In this example, a changed lockfile is not enough. A fresh observation of the deployed build and relevant conditions is needed before an authorized owner records a verified result.
Historical first-fixed releases are not current upgrade advice.
A decision can expire.
If deployed evidence becomes stale, the runtime drifts or a source correction changes the interpretation, the example finding reopens for review. Prior evidence and decisions remain in its history.
Synthetic lifecycle illustration; not a result about your system.
Integration status
Still in development.
Public reports are available without a login. The connected CLI, local workspace, agent tools and licensed enrichment are being verified separately. There is no public software checkout, promised general-availability date or approved price for connected Vigilance.
Inspect current coverage and limits ↗What a private workspace needs
- Read-only inventory imports and explicit evidence freshness.
- Unknown and conflicting conditions kept visible.
- Human authorization for decisions and exports.
- Verification tied to the deployed target.
- Signed updates and preserved local history.
Buying the Field Kit does not grant this software or enrichment access.