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

n8n-nodes-versodocs

v0.1.0

Published

n8n nodes for VersoDocs: trigger workflows on proposals, reviews and published versions, read approved docs, propose changes and review proposals.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

vytroxvytrox

Keywords

n8n-community-node-packagen8nversodocsdocumentationapprovalspecs

Readme

n8n-nodes-versodocs

n8n community nodes for VersoDocs, the document approval platform: every document has one approved Current version, and changes go through proposals and review.

  • VersoDocs Trigger: start a workflow when a proposal is opened, a proposal is reviewed, a version is published (every plan), or on any other VersoDocs event (Team plan and up).
  • VersoDocs: get a document's Current version, search approved docs, propose a change, comment on a proposal, leave an advisory review.

Install

In n8n: Settings > Community Nodes > Install, enter n8n-nodes-versodocs, accept the risk prompt. Self-hosted with npm:

cd ~/.n8n/custom && npm install n8n-nodes-versodocs

Credentials

Create an API key in VersoDocs: Organization settings > Developer > API keys (owners and admins).

| Field | Value | | --- | --- | | API Key | the vsd_... key | | Organization Slug | the part after /org/ in your VersoDocs URLs | | Base URL | https://versodocs.com (change only for staging) |

n8n tests the credential with GET /api/v1/orgs/{org}/webhooks.

Trigger

Activating the workflow subscribes a webhook through POST /api/v1/orgs/{org}/webhooks; deactivating deletes it. Set Workspace (slug or ID) when the key can see several workspaces. Each delivery is { event, created_at, data }; with Verify Signature on (default), the node checks the x-versodocs-signature-v2 HMAC with the secret returned at subscription time and rejects deliveries older than 5 minutes.

Operations and plans

| Operation | Plan / scope | | --- | --- | | Trigger: proposal opened, proposal reviewed, version published | All plans | | Trigger: every other event | Team and up | | Document: Get (Current version, by ID or path) | All plans, docs:read | | Document: Search | Team and up | | Proposal: Create (find and replace, or full Markdown) | Pro for API keys (docs:propose); never publishes | | Proposal: Comment, Review (advisory verdict) | Team and up, proposals:review |

The server enforces scopes and plans; its error message (with an upgrade link when relevant) is shown on the failing node.

Docs: https://versodocs.com/docs/automations

Develop

npm install --no-package-lock
npm run build
npm link            # then in ~/.n8n/custom: npm link n8n-nodes-versodocs

Release: bump version in package.json, merge to main, then push a matching tag (git tag n8n-v0.1.0 && git push origin n8n-v0.1.0). The publish-n8n.yml workflow publishes to npm with provenance.

License

MIT