npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@statewavedev/connectors-gitea

v0.1.0

Published

Gitea / Forgejo connector for Statewave — issues, PRs, comments, reviews, releases

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

statewavedevstatewavedev

Keywords

statewaveconnectorsgiteaforgejoaiagentsmemory

Readme

@statewavedev/connectors-gitea

Gitea / Forgejo connector for Statewave — turns repository activity into normalized episodes under repo:<owner>/<repo>.

Part of the Statewave Connectors ecosystem.

What it ingests

| Source event | Episode kind | |---|---| | Issue opened | gitea.issue.opened | | Issue closed | gitea.issue.closed | | Issue comment | gitea.issue.comment | | Pull request opened | gitea.pr.opened | | Pull request closed (not merged) | gitea.pr.closed | | Pull request merged | gitea.pr.merged | | PR comment | gitea.pr.comment | | PR review | gitea.pr.review | | Release published | gitea.release.published |

Example episode

{
  "subject": "repo:acme/widgets",
  "kind": "gitea.issue.opened",
  "text": "ada opened issue #42: CI is flaky\n\nhappens on macos runners",
  "occurred_at": "2026-05-20T09:12:00.000Z",
  "source": { "type": "gitea.issue", "id": "acme/widgets#42", "url": "https://gitea.example.com/acme/widgets/issues/42" },
  "metadata": { "issue_number": 42, "author": "ada", "labels": ["bug", "ci"], "state": "open" }
}

Run statewave-connectors sync gitea --host https://gitea.example.com --repo acme/widgets --dry-run --json to see this exact shape.

Quickstart

statewave-connectors sync gitea \
  --host https://gitea.example.com \
  --repo owner/repo \
  --dry-run

Gitea is self-hosted, so the instance URL is required: pass --host https://gitea.example.com or set GITEA_URL. GITEA_TOKEN is optional for public repositories but strongly recommended (unauthenticated reads hit lower rate limits). Both are only read by this connector.

Forgejo

Forgejo is a community fork of Gitea and exposes the same REST API (/api/v1). Point --host at your Forgejo instance and this connector works unchanged.

See the connector docs for detail: https://github.com/smaramwbc/statewave-docs/blob/main/connectors/gitea.md.

Status

v0.1.0 preview. Mapping unit-tested and smoke-validated live against Codeberg (Forgejo 15.0.0 / gitea-1.22.0) — issues, PRs, comments, reviews, releases — on 2026-05-30. Two live findings were fixed (PR-comment parent number from pull_request_url; skip REQUEST_REVIEW). See docs/forge-connectors-smoke-report.md.