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

@orchesty/connector-humaans

v2.0.2

Published

Readme

Humaans Connector

npm License

An Orchesty connector for Humaans, an HR platform for onboarding, managing, and growing employees with workflows, time-off tracking, and analytics.

Application Type

Basic

This connector authenticates using an application token sent as a Bearer token in the Authorization header.

| Field | Description | |---|---| | application_token | Your Humaans application token |

Components

| Class | Type | Description | |---|---|---| | HumaansListCompaniesBatch | Batch | Paginates through all companies (100 per page) via GET /companies | | HumaansListPeopleBatch | Batch | Paginates through all people/employees (100 per page) via GET /people |

Setup

Credentials

  1. Log in to your Humaans account.
  2. Navigate to Settings → Integrations → API.
  3. Generate a new API token.
  4. Copy the token and paste it into the Application token field in Orchesty.

API Documentation

Humaans API Documentation: https://docs.humaans.io/

Installation & Usage

Install the package:

npm install @orchesty/connector-humaans @orchesty/nodejs-sdk
# or
pnpm add @orchesty/connector-humaans @orchesty/nodejs-sdk

Register the application and nodes in your Orchesty DI container:

import { container } from '@orchesty/nodejs-sdk';
import HumaansApplication from '@orchesty/connector-humaans/dist/HumaansApplication';
import HumaansListCompaniesBatch from '@orchesty/connector-humaans/dist/Batch/HumaansListCompaniesBatch';
import HumaansListPeopleBatch from '@orchesty/connector-humaans/dist/Batch/HumaansListPeopleBatch';

const app = new HumaansApplication();
container.setApplication(app);
container.setNode(new HumaansListCompaniesBatch(), app);
container.setNode(new HumaansListPeopleBatch(), app);

License

This connector is released under the Apache License 2.0. See the LICENSE file for the full license text.

Contributing

Contributions are welcome! This connector is part of the open-source Orchesty Node.js Connectors monorepo.

For guidelines on how to create or update connectors — including project setup, coding conventions, and how to write tests — please refer to the Contributing to Connectors guide.

All contributions should include:

  • Source code in src/ following the existing connector structure
  • Tests in src/**/__tests__/ with input.json, mock.json, and output.json fixtures
  • An updated CHANGELOG.md entry