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

@fdekit/connector-jira

v0.5.3

Published

Jira connector for FDEKit

Readme

@fdekit/connector-jira

Purpose

@fdekit/connector-jira lets FDEKit agents create Jira issues through both jira.issue.create and the common issue.create capability, read linked tickets through jira.issue.get (for PR intent checks), and post status comments through jira.issue.comment. Local mode returns deterministic issues; API mode calls Jira Cloud REST.

Who should use this package

  • Deployment authors who want issue creation in Jira.
  • Recipe authors using the common issue.create capability across GitHub, Jira, and Linear.
  • Connector contributors maintaining Jira API behavior and local-mode parity.

Choose GitHub or Linear connectors when the customer issue tracker is not Jira.

5-minute quick example

import { defineDeployment } from '@fdekit/core';
import { jiraConnector } from '@fdekit/connector-jira';

const jira = jiraConnector({
  mode: process.env.FDEKIT_CONNECTOR_MODE === 'api' ? 'api' : 'local',
  projectKey: process.env.JIRA_PROJECT_KEY,
});

export default defineDeployment({
  name: 'jira-escalation',
  environment: 'local',
  connectors: { jira },
  providers: {
    mock: { name: 'mock' },
  },
  agents: {
    // ...
  },
});

Set JIRA_BASE_URL, JIRA_EMAIL, JIRA_API_TOKEN, and optionally JIRA_PROJECT_KEY for API mode.

The common issue.create priority field accepts backend-neutral labels such as low, normal, high, and urgent; the connector maps them to Jira priority names before calling the API.

Public API surface

Import from the package root:

import { jiraConnector } from '@fdekit/connector-jira';
import type { JiraConnectorOptions, CreateJiraIssueResult } from '@fdekit/connector-jira';

Root exports include jiraConnector, JiraConnectorConfig, JiraConnectorMode, JiraConnectorOptions, CreateJiraIssueArgs, and CreateJiraIssueResult. The connector family is summarized in the public API index: Public API Reference.

Stability/backward-compat notes

@fdekit/connector-jira is public but pre-1.0. The package-root factory, option/result types, local/API modes, jira.issue.create, and issue.create tool names are compatibility-sensitive.

Subpath imports are internal. Keep local mode deterministic so demos and tests do not require Jira credentials.

See also