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

@sentilis/cli

v1.1.0

Published

Sentilis CLI

Readme

Description

The Sentilis CLI is a powerful tool designed to seamlessly bridge your local development workflow with the Sentilis platform. Built on top of @sentilis/core, it enables you to confidently validate, manage, and push content directly from your terminal using simple, trackable Markdown files.

Installation

Install the CLI globally using npm:

$ npm install -g @sentilis/cli

Note: You can also execute it on the fly using npx (e.g., npx @sentilis/cli list).

Getting Started

1. Authentication

To use the CLI, you must first authenticate with your personal token.

$ sentilis auth login <your-token>

Other authentication commands:

  • sentilis auth whoami: Display the active profile.
  • sentilis auth profiles: List all saved profiles.
  • sentilis auth logout: Remove the active profile.
  • sentilis auth logout --all: Remove all saved profiles.

Global Options

  • --profile <name>, -p: Use a specific authentication profile.

2. Bio Commands

Manage your Sentilis Bio (resume / profile). New to Bios? Read What is a Bio?.

  • Push: Deploy a bio from a Markdown file or a directory of language variants. Use --dry-run to validate syntax and assets without pushing.
    $ sentilis bio push ./examples/personal-brand/bio
  • List: View your bios.
    $ sentilis bio list
  • Info: Get details of a bio, including its language variants.
    $ sentilis bio info <id>
  • Remove: Delete a bio.
    $ sentilis bio remove <id>

3. Press Commands

Manage your Sentilis Press entries and articles. New to Press? Read What is a Press?.

  • Push: Deploy an article from a Markdown directory. Sentilis automatically handles multi-file structures and assets.
    $ sentilis press push ./examples/bigtech/press/scaling-10m-rpm
  • List: View your press entries. Use --visibility to filter by access level (e.g., public, private, protected, prime). Defaults to public. Multiple values can be comma-separated.
    $ sentilis press list --visibility=public,private
  • Info: Get detailed information about a specific press entry, including its children.
    $ sentilis press info <id>
  • Remove: Delete a press entry.
    $ sentilis press remove <id>

4. Market Commands

Manage your Sentilis Market products. New to Market? Read What is Market?.

  • Push: Validate and deploy a new product from a Markdown file. Use --dry-run to validate syntax and attachments without pushing.
    $ sentilis market push ./examples/solofounder/market/lifetime-deal/lifetime-deal.md
  • List: View your published market products.
    $ sentilis market list
  • Attach: Upload a private attachment (e.g. PDF, ZIP) to an existing product, identified by ID. The file is stored privately on S3 and linked to the product.
    $ sentilis market attach <id> ./file.pdf
  • Remove: Delete a product from the market.
    $ sentilis market remove <id>

5. Sync

Validate and publish every entry under a workspace directory in one shot. A workspace is a folder containing any of bio/, press/, or market/ — typically one persona per workspace, the same layout the examples/ directory uses. Designed for the same flow locally and in CI: install, login, run sentilis sync.

  • Push everything (lenient, default): Walk the workspace, validate each entry, report issues on bad ones, and publish the clean ones. Use this when partial progress is preferable.
    $ sentilis sync ./examples/personal-brand
  • Strict mode: If any entry has validation issues, abort the whole run without publishing anything. Use this in CI to make a bad file fail the pipeline.
    $ sentilis sync ./examples/personal-brand --strict
  • Dry run: Validate everything without uploading. Combine with --strict to mirror the CI gate locally before committing.
    $ sentilis sync ./examples/personal-brand --dry-run --strict

Exit codes are pipeline-friendly: 0 only when every requested step succeeded; 1 when a publish call fails, when --strict finds issues, or when nothing publishable was found.

See the examples/ directory for real layouts (e.g. personal-brand, entrepreneur).

Stay in touch

Support

For issues and feature requests, please use the GitHub Issues page.

License

Sentilis CLI is MIT licensed. See the Contributing Guide for more details.