meerkat

private projects

Your code stays with you.

Two steps. Meerkat receives package names and versions, and never needs access to your code or repository.

§1

Two steps

  1. 01

    Create a private project.

    Name it under Projects. Meerkat gives you an upload key to set in your terminal.

  2. 02

    Run one command.

    Run it in your project folder. It scans on your machine and sends only package names and versions.

§2

Update on every merge

Save your upload key as the repository secret MEERKAT_UPLOAD_KEY, then add this file as .github/workflows/meerkat.yml.

§3

What Meerkat keeps

What does Meerkat receive?
Package names and versions.
What does it keep?
The package names, versions, project name and when the list was last updated. The uploaded file itself is not stored.
What does it never receive?
Your source code, your repository, or access to either.
Can I leave out internal packages?
Yes. In the jq line, change select(.purl) to select(.purl and (.purl|contains("your-company")|not)).
What are the limits?
5 MB and 10,000 packages per project. Upload keys are included on every plan.