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-gitlab

v0.1.0

Published

GitLab connector for Statewave — merge requests, issues, notes, approvals, releases

Readme

@statewavedev/connectors-gitlab

GitLab connector for Statewave — turns project activity into normalized episodes under repo:<group>/<project>.

Part of the Statewave Connectors ecosystem.

What it ingests

| Source event | Episode kind | |---|---| | Issue opened | gitlab.issue.opened | | Issue closed | gitlab.issue.closed | | Issue comment (note) | gitlab.issue.comment | | Merge request opened | gitlab.mr.opened | | Merge request closed (not merged) | gitlab.mr.closed | | Merge request merged | gitlab.mr.merged | | Merge request comment (note) | gitlab.mr.comment | | Merge request approval | gitlab.mr.approval | | Release published | gitlab.release.published |

System notes (state changes, label edits, etc.) are skipped — only human comments become episodes.

Example episode

{
  "subject": "repo:acme/widgets",
  "kind": "gitlab.mr.merged",
  "text": "linus merged merge request !100: Add MCP server\n\nimplements the skeleton",
  "occurred_at": "2026-05-20T09:12:00.000Z",
  "source": { "type": "gitlab.merge_request", "id": "acme/widgets!100", "url": "https://gitlab.com/acme/widgets/-/merge_requests/100" },
  "metadata": { "mr_iid": 100, "author": "linus", "labels": [], "state": "merged", "merged": true, "target_branch": "main" }
}

Run statewave-connectors sync gitlab --repo acme/widgets --dry-run --json to see this exact shape.

Quickstart

statewave-connectors sync gitlab \
  --repo group/project \
  --host https://gitlab.com \
  --dry-run

Nested groups work too — pass the full path (--repo group/sub/project); the last segment is the project, the rest is the namespace.

GITLAB_TOKEN is optional for public projects but recommended (the unauthenticated rate limit is small). When set, it is sent as the PRIVATE-TOKEN header. It is only read by this connector.

Approvals carry no per-approval timestamp on the GitLab API, so approval episodes use the merge request's updated_at as their occurred_at.

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

Status

v0.1.0 preview. Mapping unit-tested and smoke-validated live against gitlab.com (issues, merge requests, approvals, releases) on 2026-05-30 — see docs/forge-connectors-smoke-report.md. Note: GitLab requires authentication to read notes (comments) even on public projects, so unauthenticated syncs skip comments rather than fail.