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

@zapier/connectors-dev-config

v0.2.3

Published

Zapier connector policy for @zapier/connectors-dev: the @zapier/{name}-connector naming plus the license, notice, legal, folder-name, and source-url rules, shipped as an extends: preset.

Readme

@zapier/connectors-dev-config

Zapier's connector policy for @zapier/connectors-dev, shipped as an extends: preset. @zapier/connectors-dev is brand-neutral; this package layers on the Zapier-specific rules and naming the monorepo (and connector-factory) enforce.

Usage

In a repo's connectors-dev.config.ts:

import { defineConnectorsDevConfig } from "@zapier/connectors-dev";

export default defineConnectorsDevConfig({
  extends: ["@zapier/connectors-dev-config"],
});

connectors-dev validate / --fix and scaffold-connector then apply the preset below on top of the builtin rules.

What the preset enforces

  • packageNamePattern: "@zapier/{name}-connector" — every connector's package.json name is scoped ({name} is the slug / directory basename). The builtin default is the unscoped {name}-connector.
  • license — byte-identical sync of the connector LICENSE (Elastic-2.0) from this package's assets/LICENSE.
  • license-value (fixable) — the license value must be Elastic-2.0 in both package.json and the SKILL.md frontmatter. --fix writes both. The brand-neutral builtin skill-license rule only checks the two agree; this pins the value.
  • bugs-url (fixable) — package.json bugs must be https://github.com/zapier/connectors/issues, so npm's "Report a bug" link sends users to the connectors catalog's issue tracker. --fix writes the value.
  • notice — generates each connector's NOTICE from SKILL.md metadata.title.
  • legal — splices the post-H1 disclaimer (SKILL.md + README.md) and the trailing ## Legal section (README.md) from metadata.title.
  • folder-name — the connector's directory basename must equal the slug (the {name} segment of its package name): the apps/<slug>/ convention.
  • source-url (fixable) — metadata.source must be the connector's canonical GitHub permalink (https://github.com/zapier/connectors/blob/main/apps/<slug>/SKILL.md). --fix rewrites the frontmatter line. The preset drops the brand-neutral builtin source rule (ignoreRules: ["source"]) since this is a strict superset.
  • content-hygiene — agent-visible files (SKILL.md, scripts/*.ts, lib/*.ts, references/*.md, evals/evals.json) must not leak absolute filesystem paths (/Users/, C:\Users\), reference the openapi-polished.yaml build artifact, or carry a CODEGEN: polish needed marker. Reports one finding per offending line (with file + line); non-fixable. Zapier-factory-specific, so it lives here rather than in the brand-neutral @zapier/connectors-dev.
  • todo-markerSKILL.md, README.md, and every file under references/ may not carry an unresolved <!-- TODO: ... --> marker — the fill-in-the-blank placeholders scaffold-connector's templates seed for the author. Scoped to those targets rather than every .md in the connector directory so a CHANGELOG.md entry that merely mentions the marker in prose doesn't false-positive. Reports one finding per offending line (with file + line); non-fixable, since a TODO needs a human to resolve.

Each rule is also exported by name (licenseRule, licenseValueRule, bugsUrlRule, noticeRule, legalRule, folderNameRule, sourceUrlRule, contentHygieneRule, todoMarkerRule) for direct reuse or testing.