Status
Is the data fresh?
Everything healthyEvery answer basilisk gives is derived from the sources below. This page shows when each source last synced, how much of conda-forge is linked to advisory data, and how confident the matches are.
Deployment
no redeploy neededDeployed commit
38a8967d1b71
Current main
38a8967d1b71
Frontend commit
38a8967d1b71
Deploy id
31812531615-1
Backend image
rg.fr-par.scw.cloud/basilisk/basilisk-backend:38a8967d1b714297783b1d4cd07f613a86c80b6f
Frontend image
rg.fr-par.scw.cloud/basilisk/basilisk-frontend:38a8967d1b714297783b1d4cd07f613a86c80b6f
No redeploy needed: production matches current main.
Redeploy check updated just now.
Where the data comes from
Package identitieswhich conda-forge package is which14h ago
Advisories · OSVthe open-source vulnerability feed14h ago
Advisories · NVDthe national vulnerability database14h ago
conda-forge versionsevery published build basilisk knows about14h ago
How much of conda-forge is covered
linked 91%not yet linked 9% · 3,001 packages
The hatched gap is visible on purpose: for those packages, “no advisories” means “not checked”.
Every match, by confidence
39,309confirmed
9,096~ unconfirmed
327no version info
The amber and dashed columns are the review backlog for manual checks and future tooling.