Skip to content

product / releases-and-quality

Releases and quality

Know which version is really running, which error came back with it, which dependencies need an update and what holds the site back in search engines.

The live version, verified

Every GitHub tag becomes a release. It is "live" only once production really answers with that version. If an error you had resolved comes back with the new release, it reopens by itself and you know at once.

What is included
  • A GitHub App per project
  • A release is live only after production answers
  • Regressions reopened with their own alert
Read the guide
Releases

v2.4.1

9f02d17 · 3 hours ago

Live

v2.4.0

3a8c551 · 2 days ago

Previous

v2.3.9

70be2c4 · 5 days ago

Previous

Regression

ERR-1284 · reopened in v2.4.1

The dependencies to update

For each project you see the packages with a known vulnerability, how severe it is and the version that fixes it. You decide what to fix and what to ignore.

What is included
  • Counts by severity
  • The version that fixes the problem
  • Ignore with a reason
Read the guide
Vulnerabilities
critical
1
high
2
ignored
1

rack

3.1.8 → 3.1.10

Critical

nokogiri

1.16.2 → 1.16.5

High

axios

1.6.0 → 1.7.4

High

lodash

4.17.20 → 4.17.21

Medium

What holds the site back on Google

Declare a site and CloseYourIt visits it as a search engine would. Every problem has its evidence and closes by itself once you fix it. Alongside, the Web Vitals of each site.

What is included
  • Problems with their page and evidence
  • They close by themselves once fixed
  • Web Vitals per site
  • Alerts only for serious problems
Read the guide
SEO
LCP
1,9 s
INP
140 ms
CLS
0,21

Missing page titleHigh

/prezzi

Duplicate page without canonicalMedium

/blog/conserve?page=2

Image without alt textLow

/

product

The other areas