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

@rawdash/connector-linear

v0.29.2

Published

Rawdash connector for Linear — issues, cycles, teams, and users

Readme

@rawdash/connector-linear

npm version license

Sync teams, members, cycles, issues, and issue state-transition events from a Linear workspace.

Install

npm install @rawdash/connector-linear

Authentication

A Linear Personal API Key is required. It authenticates all GraphQL requests and scopes the sync to the workspaces and teams the key can access.

  1. Open Linear → Settings → API → Personal API keys.
  2. Create a new personal API key.
  3. Store it as a secret and reference it from the connector config as apiKey: secret("LINEAR_API_KEY").

Configuration

| Field | Type | Required | Description | | ----------------- | ------ | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | apiKey | secret | Yes | Linear Personal API Key. Create one at Linear → Settings → API → Personal API keys. | | teamIds | array | No | Restrict the sync to specific Linear team IDs. Omit to sync all teams the API key can see. | | resources | array | No | Which Linear resources to sync. Omit to sync all resources. The issues phase also emits state-transition events derived from each issue's history. | | historyPerIssue | number | No | How many of each issue's most recent history entries to pull. State transitions inside this window become events; an issue gaining more transitions than this between two syncs keeps only its latest. Defaults to 8. Higher values pull deeper history but lower the effective issues-per-page, since Linear scores the combined query complexity. |

Resources

  • linear_team (entity) - Workspace teams with their name and key.
    • Endpoint: GraphQL query: teams { nodes { ... } }
  • linear_user (entity) - Workspace members, including name, email, display name, and active state.
    • Endpoint: GraphQL query: users { nodes { ... } }
  • linear_cycle (entity) - Team cycles with their number, dates, progress, and final scope / completed-scope figures.
    • Endpoint: GraphQL query: cycles { nodes { ... } }
  • linear_issue (entity) - Issues with their state, priority, assignee, team, project, cycle, labels, estimate, and lifecycle timestamps.
    • Endpoint: GraphQL query: issues { nodes { ... } }
  • linear_issue_state_change (event) - State-transition events derived from each issue’s history (from-state to to-state), keyed by the originating actor.
    • Endpoint: GraphQL query: issues { nodes { history { nodes { ... } } } }
    • Derived from each issue's most recent history entries (the connector pages the history connection backward to capture the latest transitions). Only entries with a non-null fromState and toState that differ become events; these append-only events accumulate across incremental syncs. An issue gaining more transitions than historyPerIssue between two syncs keeps only its latest within that window.

Example

import {
  defineConfig,
  defineDashboard,
  defineMetric,
  secret,
} from '@rawdash/core';

const linear = {
  name: 'linear',
  connectorId: 'linear',
  config: {
    apiKey: secret('LINEAR_API_KEY'),
  },
};

export default defineConfig({
  connectors: [linear],
  dashboards: {
    product: defineDashboard({
      widgets: {
        open_issues: {
          kind: 'stat',
          title: 'In-progress issues',
          metric: defineMetric({
            connector: linear,
            shape: 'entity',
            entityType: 'linear_issue',
            fn: 'count',
            filter: [{ field: 'stateType', op: 'eq', value: 'started' }],
          }),
        },
      },
    }),
  },
});

Rate limits

Linear returns X-RateLimit-Requests-Remaining / X-RateLimit-Requests-Reset headers (reset in ms); flat resources are paged 250 at a time, issues up to 150 (capped by GraphQL query complexity against the nested history depth).

Limitations

  • API key auth only (OAuth not yet supported).
  • Webhooks and roadmap/initiative resources are out of scope.

Links

License

Apache-2.0