Skip to content
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works

How a package gets into the registry

A GitHub repository is one possible source, never the source of truth. Every version is copied, checked and approved by a person before anyone can install it, and the published bytes never change afterwards.

From a repository URL to a published version

  1. 01

    Pinned import

    The NotHoly team picks the repository. The importer resolves the exact commit and reads only that commit, so a push during the import cannot mix files from two versions.

  2. 02

    Quarantine

    The snapshot goes to private quarantine storage and nothing in it is executed: no install scripts, no dependencies, no binaries. Symlinks, submodules and LFS pointers are refused, and file count, total size, depth and compression ratio are capped.

  3. 03

    Scans

    Automated checks look for secrets, embedded links, prompt injection markers, scripts, binaries and the license. They point a reviewer at problems and do not replace the review.

  4. 04

    Diff and review

    A reviewer reads the files and the change against the last approved version, new permissions included. Every change to a package body waits for a person to approve it.

  5. 05

    Signed release

    Approval stores an immutable package with its SHA-256 and a manifest signed with the registry ed25519 key. The published version is a pointer, so a rollback moves the pointer and leaves the bytes alone.

  6. 06

    Upstream tracking

    Watched sources are checked on a schedule, daily by default. A new commit becomes a candidate in the review queue, and what you install does not change until it is approved.

After publication

Revocation
A compromised or vulnerable version can be revoked. It can no longer be installed, the CLI and the MCP server refuse it, and the version history says why.
Upstream gone
If the repository is deleted or made private, the approved snapshot keeps being served where the license allows, and the entry page says the source is unavailable.
Licenses
Each version records the license it was published under. Public on GitHub does not mean free to redistribute: when the license does not allow it, NotHoly lists the entry without serving its files.

What review does not promise

Review lowers the risk of a package; it cannot remove it. A skill is a set of instructions for your agent, and your agent acts with the permissions you give it. Read what a skill asks for before you install it, and run anything that touches a target from your own machine, inside your scope.

Report a package

If an entry looks malicious, broken or mislabeled, or you hold rights over its content, write to us through the contact page with the entry's address.
Contact the team

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login