ZipLoom
Home
PricingSign InGet Your Live URL

security

Safe-To-Launch Verdict

One Honest Answer: Yes, Not Yet, Or Unknown — And What To Fix First.

Updated

At a glance

One answer at the top of every project: safe to launch, not yet, or unknown — with the three things to fix first and a plain risk level for the app.

  • Yes Only With Evidence
  • Not Yet Means Something Specific
  • What To Fix First
Sample. One honest answer at the top of the project: yes, not yet or unknown, with what to fix first. Fix from the top, re-scan, and the verdict updates.

Why it matters

Before a launch, the question is simple: can this go live? Most tools answer with a score or a long list, and neither tells you whether the gaps that matter are closed.

The verdict answers yes, not yet or unknown. A yes needs a complete scan of your code under 30 days old with no open critical or high findings. Not yet names the findings that are in the way. Unknown means there is not enough evidence: no scan, a scan too old, or one that could not read all of your code. Up to three fixes are listed in order, and each can open as a pull request through Fix It For Me. ZipLoom checks the merged change and reports whether the finding is fixed.

Can This Go Live?Illustration · sample data
YesNot yet? Unknown1 fix2 fix3 fixpull request

What you get

Yes Only With Evidence

A yes needs a complete scan of your code under 30 days old and no open critical or high findings. An app nobody has scanned, a scan that is too old, or one that could not read all of your code reads unknown. It is never a quiet yes.

Not Yet Means Something Specific

Open critical or high findings, or a latest deploy stopped by a check, read not yet — with the findings that matter in plain words.

What To Fix First

Up to three fixes are listed with the most important at the top, each with what is wrong, where, and how to fix it.

Fix It For Me Opens The Pull Request

Each fix can open as a pull request that you review and merge. ZipLoom never merges it. After you merge, ZipLoom scans the change and tells you whether the finding is fixed, still there, or could not be checked.

A Plain Risk Level For Each App

Owners and Admins also see a risk level for each app — Low, Guarded, Elevated or High — and a hardening plan. It is a word and a plan, never a score, and it is available on every plan.

How It Works

  1. 1

    Scan your project. The verdict reads the same findings your Findings page shows.

  2. 2

    The verdict at the top of the project page reads yes, not yet or unknown, with the reason.

  3. 3

    Fix the listed items from the top. Findings you have triaged as an accepted risk or a false alarm are not counted, and the verdict says how many so it is never silent.

  4. 4

    Re-scan. The verdict updates when the new scan completes.

What this check inspects

  • The newest completed scan of your code: whether it finished, whether it read everything, and how old it is.

  • Open critical and high findings from that scan, after your own triage decisions.

  • Whether the latest deploy was stopped by a check, or a check could not finish.

What it means when this fails

A verdict that always says yes is decoration. When ZipLoom cannot tell, it says unknown and tells you why, so a missing scan is never mistaken for a clean one.

What it does not do

  • A yes is not a guarantee that the app is secure. It means a complete, recent scan found no open critical or high issue you have not triaged.

  • ZipLoom never merges a fix. A person reviews and merges every pull request.

Questions

Does a yes mean my app is secure?
No. It means a complete, recent scan found no open critical or high issue that you have not triaged. ZipLoom's checks do not catch everything, and a yes is not a guarantee.
Does ZipLoom fix things for me?
It can write the fix: Fix It For Me opens a pull request on a branch of your repository, and a person reviews and merges it. ZipLoom never merges it and never pushes to your main branch. Each fix it proposes is checked before the pull request opens, and some changes are refused rather than proposed. It is available on every plan to members who can edit; checking a merged fix uses one scan from your allowance.
Who can see the risk level?
Owners and Admins of the workspace, on every plan. The per-finding priority word shows to any member who can see the finding.

Related features