Since the 🚀 we've identified several issues and improvement opportunities which we already addressed. We are tracking around 100 issues on a private board and from now on we are aiming for a regular release cycle at the beginning of each month.

We will be using the featurebase feedback section to keep track of user-feedback / feature requests only or to ask for feedback whenever we are planning a major change. Issues we identify along the way or plans (other than user-submitted ones), will be tracked privately to avoid clutter.

v0.1b introduces ~20 fixes / improvements:

✅ Under the hood:

• increased session time duration

• major SQL overhaul --> we have improved percentile calculations to be more efficient and also spread SQL load across multiple threads. You should notice much faster load time (especially for the monthly view)

• fixed reset password

• fixed oauth login sometimes failing

• fixed regular login sometimes failing

✅ APP Logic:

• we are recalculating EPSS percentile based on the EPSS score. Previously we were pulling EPSS percentile from first.org but we realized that we are only pulling a subset of the data (CVE-2024-XXXX) and first.org percentile is calculated based on the entire set (all CVEs)

• major rework for percentile calculation. All views now use the same improved formula

• when selecting a date range, now we only calculate the average for Social, Threat & EPSS. We calculate the scores for each large fingerprint run (2 times per day). We moved away from using avg() as this only works well when there is data available. Now we are averaging by datediff() + 1

• fixed an issue with the charts not loading whenever you would access the detailed view for the first time

• fixed search & alerts not returning any results when searching for a CVE

• fixed NVD score not showing up sometimes in detailed view

✅ Various small UI/UX improvements

If you notice any issues please do submit them via the feedback section.

In the next version we will be focusing on:

1. becoming "business ready" in anticipation of a future API plan 🏢

2. low hanging fruits or critical issues 🚨

3. listening to user feedback 🗣