Skip to content
Demo data.
Fendix logo

Historical synthetic snapshot

Decision Intelligence demo

Explore the real workspace components with fictional evidence. No account, customer records or scan requests.

At this point in the timeline, the newest completed scan has complete coverage. The absent credential is no longer detected; this does not claim an engine-verified fix.

Read the technical guide
Back to scans

demo-orders

Completed

Jul 21, 2026, 09:00 AM · 60.0s · whitebox mode

Release decision

BLOCK

3 findings meet the configured fail-on threshold, so this release is blocked.

Coverage
Required coverage complete
Policy
2.0.0
Fails on
HIGH and above
Engine
3.7.0
Scanned
Jul 21, 2026, 09:00 AM
Decided
Jul 21, 2026, 09:01 AM(2 days ago)
  • A newer scan of this target recorded a decision on Jul 23, 2026, 09:00 AM. This one stays as recorded; it is no longer the target's latest.
  • A newer scan of this target is running.

Blocking findings

Next steps

A release decision is a recommendation, not an approval. Your team stays accountable for the release.

Recommended next actions

Ordered by priority. Priority orders the work; it never changes the release decision.

Verification reads the newest later completed scan of this target, from Jul 23, 2026, 09:00 AM:BLOCKOpen that scan

A newer scan is still running; it is not read as evidence until it completes.

2 active actions; 1 closed.

  1. P1: act firstState: Still detectedEvidence: Confirmed shared remediation point

    Upgrade demo-package in requirements.txt (installed: 1.0.0)

    Linked findings

    Steps

    1. Review each advisoryAdvisories: DEMO-ADVISORY-1, DEMO-ADVISORY-2
    2. Check whether one version contains the fix for every listed advisory
    3. Update the lockfile and run the tests
  2. P2: nextState: Still detectedEvidence: Potential relationship

    Investigate the related findings in app/orders.py

    Linked findings

    Steps

    1. Inspect the related findings togetherFile: app/orders.py
    2. Fix each finding on its own unless one change is shown to address several

Recommendations are deterministic and never change the release decision; nothing is changed in your code.

Coverage

5 findings

Finding decision
Severity

Each finding has its own decision. The release decision above is made once, for the whole scan.

DEMO-1CRITICALFinding decision: BLOCKWhite-boxIllustrative package advisory A

Finding decisionBLOCKConfidence-gated policy

Confidence: HIGH

Evidence

Synthetic evidence for product education; no customer record or credential.

Remediation

Review each illustrative advisory before choosing an upgrade; no combined fixed version is asserted.

References: DEMO-ADVISORY-1
DEMO-2CRITICALFinding decision: BLOCKWhite-boxIllustrative package advisory B

Finding decisionBLOCKConfidence-gated policy

Confidence: HIGH

Evidence

Synthetic evidence for product education; no customer record or credential.

Remediation

Review each illustrative advisory before choosing an upgrade; no combined fixed version is asserted.

References: DEMO-ADVISORY-2
DEMO-5CRITICALFinding decision: BLOCKWhite-boxCredential in source

Finding decisionBLOCKConfidence-gated policy

Confidence: HIGH

Evidence

Synthetic evidence for product education; no customer record or credential.

Remediation

Review the illustrated evidence, apply the appropriate change, then re-scan with the same scope.

Location: config/credentials.py:26References:
DEMO-3HIGHFinding decision: WARNWhite-boxUnsafe query in export

Finding decisionWARNConfidence-gated policy

Confidence: MEDIUM

Evidence

Synthetic evidence for product education; no customer record or credential.

Remediation

Review the illustrated evidence, apply the appropriate change, then re-scan with the same scope.

Location: app/orders.py:18References:
DEMO-4HIGHFinding decision: WARNWhite-boxUnsafe command in export

Finding decisionWARNConfidence-gated policy

Confidence: MEDIUM

Evidence

Synthetic evidence for product education; no customer record or credential.

Remediation

Review the illustrated evidence, apply the appropriate change, then re-scan with the same scope.

Location: app/orders.py:22References: