Skip to main content

oss-intake

ci codeql OpenSSF Scorecard PyPI OpenSSF Best Practices

Know which of your open source is malicious, exploited or going stale, and what to do about each one.

Most of every application is open source, and most organisations check a package once, when it is approved, and never again. A package that was clean on approval day can turn hostile later: in September 2025 attackers published malicious releases of chalk, debug and other npm packages downloaded billions of times a week. Log4Shell is still exploited years after its fix shipped. oss-intake checks what you run against public advisory and exploit data and gives one reading order: remove what is malicious, patch what is being exploited, schedule the rest.

Try it in 30 seconds

No scanner, no account and no file needed:

pipx install oss-intake
oss-intake --package npm:chalk@5.6.1 --package maven:org.apache.logging.log4j:log4j-core@2.14.1 \
  --package pypi:requests@2.34.2 --out demo-report

Among its progress and warning lines, it prints a verdict for each package:

findings=9 critical=2 high=1 with_fix=8 fix_before_release=0 fix_date_unknown=0
  chalk 5.6.1 (npm): MALICIOUS release. Remove it.
  org.apache.logging.log4j:log4j-core 2.14.1 (maven): 8 known vulnerabilities, 2 critical, 2 known exploited; upgrade to at least 2.25.4 (clears all known)
  requests 2.34.2 (pypi): no known vulnerabilities

demo-report/executive-summary.html is the page for someone who will not read a findings list:

oss-intake executive summary: 3 packages checked, 2 to act on now, chalk 5.6.1 malicious (remove, do not patch), log4j-core 2.14.1 known exploited (upgrade to 2.25.4)

Build the command

oss-intake has 70 options; most runs need three. The command builder takes a link, an install command or a file name you paste (or asks what you are checking), then gives the command for bash, zsh or PowerShell and says in plain words what it will check, what it sends where, and when it fails. It runs in your browser and sends nothing anywhere.

Using the command builder: pick a dependency list, give the lockfile, ask to fail on malware, review what the command will do and copy it; then the report shows six malicious packages

45 seconds: the questions, copying the command, and the report for a lockfile of six compromised npm releases, from a real run of the same command. Full-quality video.

The gaps it closes

Questions a security or engineering manager gets asked, and what answering them usually takes:

The question Usually With oss-intake
Are we running any of the compromised packages in the news? Someone searches repositories by hand One run over your package list or SBOMs; malicious releases come first, marked "remove, do not patch"
Which of our thousands of findings are actually being exploited? Scanner output sorted by CVSS Findings ordered by CISA KEV, public exploits and EPSS; ones that apply only under stated conditions are set apart
Has anything changed since we approved it? Checked once, at approval A ready-made weekly re-scan that opens an issue when something new needs action, with the assessor's decisions carried between runs
What does upgrading buy us, and who has to do it? A spreadsheet and a lot of chasing Known vulnerabilities now, after the minimum fix and after the latest release, with totals by owner or team
Does this project or vendor actually ship fixes? Gut feel Release lag (how long fixes existed upstream before the project shipped them), release cadence and OpenSSF Scorecard
Can we block it in the pipeline? Custom scripts --fail-on malicious,kev exits non-zero, and a check that could not run fails rather than passing

What you can point it at

You have Run Scanner needed
A package name and version --package npm:chalk@5.6.1 (repeat it, or give a pkg: purl) No
A list of packages, from Artifactory, Nexus or a spreadsheet --path packages.csv No
SBOMs: CycloneDX, SPDX or GitHub's dependency-graph export, one file or a folder --path ./sboms No
Laptops and servers the osquery collector makes one SBOM per host No
What a Nexus proxy has cached the Nexus collector No
An R renv.lock --path renv.lock No
A lockfile: npm, Python, Maven, Go, Rust, PHP, Ruby or .NET --path package-lock.json Trivy
A JAR, WAR, EAR or binary, also checked against the registry's published checksum --path app.jar Trivy
VS Code extensions: a .vsix, or everything installed, also checked against the Marketplace's removal list --path ~/.vscode/extensions Trivy
A container image --image owner/app:1.2.3 Trivy (Grype optional)
A GitHub project --repo owner/name: alone for project health; with an image, artifact or lockfile, also release lag No

It is free and open source (Apache-2.0) and runs on Windows, macOS or Linux with Python. Your files are read where they are: what leaves the machine is package names and versions, vulnerability IDs and, with --repo, the repository name, sent to public services such as OSV, deps.dev, the package registries, FIRST EPSS, OpenSSF Scorecard and GitHub (with your GITHUB_TOKEN, if set, sent only to api.github.com). It does not prove a vulnerability is exploitable in your environment, and it says so in every report; see What it does not do below.

Install

Python 3.10 or later on Windows, macOS or Linux. No administrator rights are needed.

pipx install oss-intake

On Windows without pipx: py -m pip install --user pipx, then py -m pipx ensurepath, open a new terminal and run pipx install oss-intake. Container images, lockfiles and built files are scanned with Trivy (and Grype if you have it); package names, package lists and SBOMs need no scanner. The guide shows how to install the scanners pinned and verified, and how to verify an oss-intake release.

What it does not do

  • It does not prove exploitability. Scanners match component versions against advisory databases. A finding means a version is listed as affected, not that the vulnerable code is reachable or exposed in your deployment. The CSV has triage_* columns for the assessor's decisions, which carry over to the next run.
  • It does not install, download, bundle or redistribute scanners. You install them; it verifies them.
  • It does not assess licences, secrets or misconfiguration, and it does not detect new malware. Package versions already known as malware are flagged as malicious: listed in the OpenSSF malicious packages database (OSV MAL- entries), or covered by an advisory classed as embedded malicious code (CWE-506), as the compromised ua-parser-js 0.7.29 and event-stream 3.3.6 releases are.
  • It does not give a risk rating. The likelihood suggestion is a starting point for an assessor.
  • It does not fix anything or open issues upstream.

Learn more

Licence

Apache License 2.0. See LICENSE.

Metadata

Release files for oss-intake 0.16.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for oss-intake 0.16.0
File Size Uploaded Provenance Actions
oss_intake-0.16.0.tar.gz 522.3 kB With provenance Details for oss_intake-0.16.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for oss-intake 0.16.0
File Interpreter ABI Platform Actions
oss_intake-0.16.0-py3-none-any.whl Python 3 none any Details for oss_intake-0.16.0-py3-none-any.whl

Total release size: 719.9 kB

Release files / oss_intake-0.16.0.tar.gz

Download URL oss_intake-0.16.0.tar.gz
Size 522.3 kB
Tags Source
SHA-256 checksum
How to use checksums
11f1f847daae4209f11574028e6236a7c41fedca1fac6726a9cd3b1b3c7afa06
BLAKE2b-256 checksum
How to use checksums
36232c4ab2886328f476a5a579e3285a14bc689115f99316dc92c21a849210af
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 6, 2026.

Transparency log

Release files / oss_intake-0.16.0-py3-none-any.whl

Download URL oss_intake-0.16.0-py3-none-any.whl
Size 197.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
1d0fa2ad2adf52316d8213363cfc7ec40fc482cab105947b8e5ad5f41de3ddbc
BLAKE2b-256 checksum
How to use checksums
a04274e6316bf8511b403eaa0cb2cb36ba160cb2b3c151662f73589d8e62b9d8
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 6, 2026.

Transparency log

Security for oss-intake 0.16.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for oss_intake-0.16.0.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 6, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page