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

maloss

v0.3.0

Published

MALOSS (pronounced "malice"), scans package manifest files to see if any of the libraries and packages are malicious.

Readme

MALOSS - Identify Malicious Open-Source Software

MALOSS

MALOSS (pronounced "malice"), scans package manifest files to see if any of the libraries and packages are malicious. It does this by analyzing local package manifest files, or remote package files, and checking both OSV and GitHub Security Advisory (GHSA) for known malicious packages.

Incredibly, SCA tools don't help you identify malicious packages. I know, this is crazy, but its true. MALOSS is the missing piece to the SCA puzzle that I needed but couldn't find. You can use MALOSS manually at the command line, but you can also use it in you CI/CD pipelines and to scan GitHub, GitLab and other repos directly.

Installation

npm install maloss

How to use MALOSS

Scan local package.json file

maloss package.json

Command Line Options

  • --remote, -r: Remote mode - scan remote files via URLs
  • --json, -j: JSON mode - outputs structured JSON data instead of human-readable format
  • --output, -o: Write report to specified file instead of console output
  • --no-color: Disable colored output (useful for logs or unsupported terminals)

Supported File Types

  • package.json - Node.js dependencies
  • package-lock.json - Node.js lockfile with exact versions
  • pyproject.toml - Python project dependencies (PEP 621, Poetry, etc.)
  • requirements.txt - Python requirements file

More detailed usage examples

Scan local requirements.txt

maloss requirements.txt

Scan remote package file

maloss -r https://github.com/oven-sh/bun/blob/main/package.json

Write Human-Readable Report

maloss package.json --output report.txt

Creates report.txt:

Scanning ./tests/malicious/package.json...
Found 3 packages in ./tests/malicious/package.json
Checking 1/3: validate-rb
Checking 2/3: express-exp
Checking 3/3: prettier

==========================================================================
MALOSS - MALICIOUS PACKAGE REPORT
==========================================================================

Total packages scanned: 3
Malicious packages found: 2

Findings by severity:
  Malware: 2

Detailed findings:
--------------------------------------------------------------------------

📦 Malicious Package: validate-rb
🆔 ID: MAL-2025-5294 (https://osv.dev/vulnerability/MAL-2025-5294)
⚠️  Severity: Malware
🔍 Source: OSV
📝 Summary: Malicious code in validate-rb (npm)
🎯 Affected versions: 1.0.0

📦 Malicious Package: express-exp
🆔 ID: MAL-2025-3238 (https://osv.dev/vulnerability/MAL-2025-3238)
⚠️  Severity: Malware
🔍 Source: OSV
📝 Summary: Malicious code in express-exp (npm)
🎯 Affected versions: 1.0.1

Create JSON Report

maloss package.json --json --output report.json

Creates report.json:

{
  "analyzed_by": "MALOSS at 2025-06-30T10:05:01.590757",
  "total_packages_scanned": 3,
  "malicious_packages_found": 2,
  "remote_source": null,
  "findings": [
    {
      "package_name": "validate-rb",
      "id": "MAL-2025-5294",
      "severity": "Malware",
      "source": "OSV",
      "summary": "Malicious code in validate-rb (npm)",
      "affected_versions": [
        "1.0.0"
      ],
      "url": "https://osv.dev/vulnerability/MAL-2025-5294"
    },
    {
      "package_name": "express-exp",
      "id": "MAL-2025-3238",
      "severity": "Malware",
      "source": "OSV",
      "summary": "Malicious code in express-exp (npm)",
      "affected_versions": [
        "1.0.1"
      ],
      "url": "https://osv.dev/vulnerability/MAL-2025-3238"
    }
  ]
}

No Vulnerabilities Found

maloss package.json --output report.txt

Creates report.txt:

==========================================================================
MALOSS - MALICIOUS PACKAGE REPORT
==========================================================================

Total packages scanned: 3
Malicious packages found: 0

✅ No known malicious packages found!

CI/CD Integration Examples

Generate Reports for Artifacts

# Generate human-readable report for review
maloss package.json --output report.txt

# Generate JSON for automated processing
maloss package.json --json --output security-scan.json

Archive Reports

# Generate timestamped reports
DATE=$(date +%Y%m%d-%H%M%S)
maloss package.json --output "report-$DATE.txt"
maloss package.json --json --output "report-$DATE.json"

Exit Codes

  • 0: No vulnerabilities found
  • 1: Vulnerabilities detected (useful for CI/CD pipeline failures)

Features

  • 🔍 Scans for malicious packages using OSV (MAL- advisories) and GitHub Security Advisory
  • 📄 Supports multiple package manifest formats
  • 🎨 Colored terminal output with bright red highlighting for malicious packages
  • 📊 JSON output mode for CI/CD integration
  • 💾 File output for reports and archiving
  • 🚀 Perfect for automated security scanning in development workflows