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

tangkal

v1.3.1

Published

Preventive security scanner for cloned repositories. Detects malicious AST patterns, vulnerable dependencies, and typosquatting.

Readme

Tangkal 🛡️

Tangkal (Indonesian for "ward off" or "repel") is a lightweight, preventive security scanner designed to inspect cloned repositories before you run npm install.

It is specifically built to detect malicious patterns often found in "Job Scam" repositories, such as:

  • Obfuscated Code: Base64 (atob, Buffer), Hexadecimal strings.
  • Dynamic Execution: eval, new Function.
  • Hidden Network Calls: Fetching payloads from remote URLs (e.g., JSON keepers).
  • Dangerous Lifecycle Scripts: preinstall, postinstall in package.json.
  • Typosquatting: Detects packages with names deceptively similar to popular libraries (e.g., react-doom vs react-dom).
  • Vulnerability Scanning: Aggregates data from OSV, Snyk, and Exploit DB to report known vulnerabilities.
  • Safe Installation: Prompts to safely install dependencies using the detected package manager (npm, yarn, pnpm, bun, deno) only if the scan is clean.

Installation

From Source

git clone https://github.com/yourusername/tangkal.git
cd tangkal
npm install
npm link

Usage

Run tangkal against any suspicious directory:

tangkal ./path-to-suspicious-repo

Or simply inside the directory:

cd suspicious-repo
tangkal .

Output Example

Tangkal separates findings into two clear categories: Malicious Code and Vulnerable Packages.

====================================
ALERT: Malicious Code Detected
====================================
File: src/utils.js
Line: 45
Suspicious pattern detected.
Code: new Function("return " + decodedPayload)()

====================================
ALERT: Vulnerable Package
====================================
[SOLUTION]: Upgrade [email protected] to [email protected] to fix.
[HIGH Severity] [https://osv.dev/vulnerability/GHSA-xxx] [Snyk: https://security.snyk.io/vuln?search=CVE-2021-23337]
[email protected] Prototype Pollution
introduced by [email protected]

How to Test

To safely test Tangkal's detection capabilities without risking your main environment, we recommend using our dedicated vulnerability test repository.

git clone https://github.com/AlphaByte-RedTeam/vuln-test
cd vuln-test
tangkal .

Disclaimer

This tool uses heuristic pattern matching. It may produce false positives (e.g., in build scripts or test files) and cannot guarantee 100% safety. Always review code manually if you are unsure.