security
Security Advisories & Package Alerts
When A Popular Package Breaks, Find Out Whether It Is In Your App.
Updated
Share This With A Builder Who Needs It
Know someone shipping AI-written code? Send them this walkthrough.
At a glance
Security advisories matched to your own apps, a free re-scan of affected projects, and an alert when a package you use is newly listed as exploited.
- Am I Affected? Answered
- Affected Projects Re-Scanned For Free
- Approved By A Person
Why it matters
The first question after a big vulnerability announcement is whether it affects you. Answering it usually means reading advisories by hand and checking each app's dependencies.
Each ZipLoom advisory says whether it matches your workspace, from the packages your scans found and the packages your lockfiles install. Affected projects are queued for a fresh scan that does not count against your allowance. Between advisories, package alerts email Owners and Admins when a package you use is newly listed by CISA as exploited, or when public attack forecasts for it jump within a week. A person at ZipLoom approves every advisory and every message before it goes out.
What you get
Am I Affected? Answered
Each advisory says whether it matches anything in your workspace, based on what your scans found and the packages your lockfiles install.
Affected Projects Re-Scanned For Free
Projects an advisory touches are queued for a fresh scan, and those re-scans never count against your monthly scan allowance.
Approved By A Person
Every advisory, and every message about it, is reviewed and approved by someone at ZipLoom before it goes out.
Package Alerts Between Scans
If a package you use is newly listed by CISA as exploited in the wild, or public forecasts of attacks on it jump within a week, Owners and Admins get an email and the dashboard shows a banner.
A Text Only If You Ask For One
Where text messages are available, you can opt in to a text for incidents that affect apps like yours. It is off unless you tick it, and STOP turns it off. Email alerts never depend on it.
How It Works
- 1
Open Security → Advisories to read published advisories and whether each one matches your workspace.
- 2
When an advisory matches, your affected projects are re-scanned and the new findings appear in Security → Findings.
- 3
Package alerts arrive by email to Owners and Admins; add Slack or a webhook in Settings → Alerts if you want them there too.
- 4
Optional: verify your mobile number in Settings to receive incident texts.
What this check inspects
The packages your scans found and the packages your lockfiles install.
Public exploitation records (CISA's Known Exploited Vulnerabilities list) and public attack forecasts for the packages in your open dependency findings.
What it means when this fails
The first question after a big vulnerability announcement is whether you are affected. Without a match against your own apps, that answer means reading every alert yourself.
What it does not do
A package alert repeats what public sources say about a package. It does not mean your app was attacked.
Text alerts are opt-in and only where text messages are available. Email alerts never depend on them.
Questions
- Does a package alert mean my app was attacked?
- No. It repeats what the public sources say about the package. It is a reason to update, not a report of an attack on you.
- Can I see advisories without an account?
- A public list at ziploom.dev/advisories shows each advisory's id, date and scope. The full advisory and whether it affects you are inside ZipLoom.
- Which plans include advisories?
- Every plan.
Related features
Vulnerable Dependency Audit
Every Installed Package Against OSV — Critical CVEs And Malware Block The Deploy.
Learn moreSlack & Webhook Alerts
The Deploy Events You Choose, Sent Where Your Team Already Works.
Learn moreSecurity Scan On Every Deploy
Catch RLS Gaps, Secret Leaks, And CVEs Before Your App Is Reachable.
Learn more