Product
Recent improvements
Last updated:
Veripsa ships frequent small improvements. This page shows what changed on the product surface, not internal version numbers — we don't track semver. The list is reverse-chronological; newest entries are at the top.
What goes here, and what does not
We list user-visible changes — wording corrections on the verdict comment, new behaviors in the GitHub App, new pages on this site. Each entry is one or two sentences in plain language, describing what changed on the surface, not how we built it.
Internal refactors, dependency bumps, and routine deploys are not listed here. Those live in the engineering log and don't change how the product behaves for you.
Recent entries
Simpler onboarding, and a link to the Japanese launch article
The install-to-first-check path in the docs and /how-it-works was simplified, and the newsletter page now links the Japanese launch article on Zenn for readers who want the story behind the product.
First-run dashboard now says what is happening
Right after install, the signed-in dashboard shows which repositories Veripsa Core is watching instead of a quiet empty state, so a calm first day doesn't read as "nothing is working".
Security and trust pages state more of what is already true
/security now states that stored operational data is encrypted at rest, and the Trust Center names the hosting subprocessor explicitly (EN and JA).
The guided sandbox leads with a real result
/try now opens with a link to a completed public run — the real check on a real pull request — before asking you to fork anything (EN and JA).
"I already use git worktrees" is answered on the comparison page
/compare now explains where worktrees help (isolated checkouts while agents work) and what they don't decide (how the resulting open PRs land together on main) — EN and JA.
Homepage proof link points at a live public check again
The "see a real check on a public PR" link on the homepage was repointed at a live public example, with an automatic link check to catch future breakage.
Japanese blog restored
/ja/blog is available again after a routing regression briefly made it unreachable.
Pricing FAQ corrected for private repositories on GitHub Free
The pricing FAQ again carries the caveat that required status checks on private repositories depend on your GitHub plan.
Onboarding and evaluation copy clarified
The docs onboarding guide, /how-it-works, and the evaluation pages were tightened: clearer install steps, clearer wording about what the check shows in each state, and shorter evaluation copy on the homepage.
Dashboard shows an explicit notice when GitHub install info is unavailable
If GitHub can't confirm your installations for a moment, the signed-in dashboard now shows a clear notice instead of an empty list, so a temporary lookup failure doesn't read as "nothing installed".
/example merged into the dashboard demo
The separate /example page now redirects to the verdict section of the dashboard demo (same for the Japanese mirror), so there is one current demo surface instead of two that could drift apart.
Customers page refocused on evaluation
The customers page no longer presents a case-study preview. Until named customer stories exist, it provides a short evaluation path: demo, docs, trust notes, and the install link.
Trust Center trimmed to current practice
Two forward-looking sections (a pre-launch posture summary and a procurement roadmap) were removed from the Trust Center, so the page states only current, verifiable practice.
More precise wording about what is covered
Public pages that read as if the check runs on all pull requests now say "covered pull requests", and the Japanese pages describe a soft pause as responding to strong collision risk rather than a confirmed collision. The copy now matches how coverage and verdicts actually behave.
Public GitHub resources are now grouped under GetVeripsa
Public Veripsa resources now have three clear entry points under GetVeripsa: organization policy, the integration and data-handling contract, and the hands-on collision lab. Product behavior stays inspectable; the Core implementation is not published.
Verdict wording — "advisory by default"
The verdict comment now says "advisory by default" instead of "won't block your merge" when branch protection is not configured. The check is informational; whether it acts as a gate depends on your branch-protection settings, not on the comment text.
Check details link goes to the verdict comment
Clicking "Details" on the Veripsa check now opens the verdict comment on the pull request directly, instead of the commit page. One fewer hunt to find the read-out.
Reduced "git conflict" overclaim
When two pull requests touch related code rather than the exact same text, the verdict no longer suggests a textual git conflict. The wording is softened to describe the actual signal.
Unresolved conflict markers are surfaced before merge
If a pull request would land with unresolved git conflict markers in the diff, Veripsa now surfaces it on the check so the team can fix it before merge. This catches a common failure mode where an AI agent declares a rebase done but leaves the markers behind.
Draft pull-request analysis
Draft pull requests now get the same verdict as ready pull requests, so the draft window can act as a scout for downstream impact before review starts. Wording on the verdict comment indicates the pull request is still a draft.
Unity (.cs) support
Veripsa now covers C# files used by Unity projects, which improves verdict precision on Unity codebases. Files that were previously "unknown — language not yet supported" are now covered.
"Unknown" distinguishes new files from unsupported languages
When the verdict is "unknown", the comment now tells you whether the file is new in this pull request (no prior signal to compare against) or whether the language is not yet supported.
Free access page reflects the early-access launch path
The free access page now sends users to GitHub App install, says Veripsa Core is free while in early access, and keeps checkout out of the active flow.
Japanese translations across the marketing site
Japanese versions of the marketing, docs, free access, compare, trust, fit, dashboard demo, how-it-works, newsletter, customers, incidents, status, and blog pages are now available under /ja.
Decision pages added
Trust Center, /compare, /docs, /how-it-works, /fit, /newsletter, /incidents, /status, and /customers are now available on the site.
We don't link to internal pull requests or commits from this page on purpose — what matters here is what changed for you, not how it was implemented.
For the observable integration and data boundary, see github.com/GetVeripsa/veripsa-webhook-spec. The private decision engine is not published.