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

issue-mapper

v0.2.2

Published

CLI tool for mapping issues across platforms

Readme

Issue Mapper

CLI tool for mapping issues across third party platforms.

Whether you call them issues (in the case of git), cards (in the case of Trello)) they all share a similar purpose: To keep track of progress for a particular feature that needs to be worked on

They also share multiple common features:

  • An issue can have a title & description
  • An issue can have any number of attachments
  • Most importantly, and issue hosts a discussion thread or comments
  • Additionally issues can have labels, assignees, dues date & many other platform specific features

The purpose of this tools is to create a uniform layer for mapping from input to output

Install

  1. git clone [email protected]:felipearosemena/issue-mapper.git
  2. cd issue-mapper

Configuration

The mapper uses each platform's APIs under the hood to get & post issues.

You must make sure to populate the .env file with the required API credentials for the platforms you're going to work with.

Use .env-sample as your starting point to config your own credentials.

Usage

node index.js --i <input-name> --o <output-name> <arguments>

Each mappping has it's own set of specific required arguments. See below.

Mappings

Trello

.env credentials

TRELLO_APP_KEY : Your trello application key TRELLO_USER_TOKEN : Trello unique user token

Command Arguments

--trello_board_id : Id for the board you want to get/post cards

Gitlab

.env credentials

GITLAB_TOKEN : Gitlab private token

Command Arguments

--gitlab_project_id : Name of the project you want to get/post issues. The name must contain the username + project name.

Example my-gitlab-user/my-awesome-project

Sample Usage

Get trello cards & map them over to git lab

node index.js --i trello --trello_board_id <trello-board-id> --o gitlab --gitlab_project_id <my-gitlab-user/my-awesome-project>