go-gitea/gitea dependency check
Git with a cup of tea! Painless self-hosted all-in-one software development service, including Git hosting, code review, team collaboration, package registry and CI/CD
go-gitea/gitea: 2 findings to fix, none critical, 1 with a known fix.
2 things your coding agent doesn’t know about this repo
go-gitea/gitea on GitHub (opens in a new tab)
2 warnings5 low priority
One task with every fix, most urgent first, the file to change and why. Paste it into Claude Code, Cursor or Codex.
- WarningVulnerabilitygo.mod
GO-2026-5932 in golang.org/x/crypto 0.57.0
The golang.org/x/crypto/openpgp package is unmaintained, unsafe by design, and has known security issues
0.57.0No fixed version yetView advisory, source: OSV.dev (opens in a new tab) - WarningEnd of lifepackage.json
Tailwind CSS 3.4 reaches end-of-life in 134 days
Support ends 2027-02-28. Plan an upgrade to Tailwind CSS 4.3.
Checked 326 packages and 2 base images from go.mod, package.json, pyproject.toml, pnpm-lock.yaml and 2 more against:
Add this badge to your README
It shows today’s result and links to this report, so anyone opening the repo sees what needs fixing.
[](https://stackprism.ai/check/github/go-gitea/gitea)What next
Want your agent to check before it adds a package? Connect Claude Code, Cursor or Codex to StackPrism. Setup steps
Ask Prism Agent about go-gitea/gitea
Map the repo (free) and ask what to fix first, whether an upgrade is safe, or what breaks if a service goes down. Prism Agent checks live sources before it answers.
How this report works
StackPrism read go.mod, package.json, pyproject.toml, pnpm-lock.yaml and 2 more from the default branch of go-gitea/gitea and checked its 326 packages and 2 base images against GitHub, OSV.dev, deps.dev, endoflife.date, npm and PyPI. Nothing was installed or run, and there’s no AI in the findings: each one comes from a source you can open.
Vulnerabilities come from OSV.dev, with known-exploited ones from CISA marked and listed first. Runtimes, frameworks and base images are checked against endoflife.date, and packages against their registry for deprecations and major versions you’ve fallen behind. The fix task above lists every change with the file to edit.
This page refreshes every few hours; after you push a fix, “Check again” runs it now. Only the repo’s root is read. For an app in a sub-folder, paste the folder’s link into the dependency check, and for a private repo, connect GitHub.