gitwtfhub

wtf is nope_modules?

patrickjs/nope_modules — explained in plain English

Analysis updated 2026-07-17 · repo last pushed 2026-05-22

★ 1JavaScriptAudience · developerComplexity · 2/5MaintainedSetup · easy

TL;DR

A safety-first CLI tool that finds stale, untouched projects and deletes their node_modules folders to free up disk space.

Mindmap

mindmap
  root((nope_modules))
    Inputs
      Code folders
      Age threshold
    Outputs
      Cleanup report
      Freed disk space
    Use Cases
      Reclaim disk space
      Automate monthly cleanup
    Tech Stack
      JavaScript
      Node.js
      Git
    Audience
      Developer

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Why would anyone build with this?

REASON 1

Scan a folder of old side projects to find how much disk space stale node_modules folders are wasting.

REASON 2

Review a generated Markdown/JSON report before approving deletion of any node_modules folders.

REASON 3

Set up a monthly automatic scan on macOS to keep track of reclaimable disk space over time.

REASON 4

Safely clean up dozens of untouched cloned repos without risking active or symlinked projects.

What's in the stack?

JavaScriptNode.jsGit

How it stacks up

patrickjs/nope_modules0xmukesh/docusaurus-tutoriala15n/andrewscheuermann
Stars111
LanguageJavaScriptJavaScriptJavaScript
Last pushed2026-05-222021-12-272015-01-11
MaintenanceMaintainedDormantDormant
Setup difficultyeasyeasymoderate
Complexity2/52/51/5
Audiencedeveloperdevelopergeneral

Figures from each repo's GitHub metadata at analysis time.

How do you spin it up?

Difficulty · easy Time to first run · 5min

Zero runtime dependencies, a standalone script, deletion always requires an explicit second command with --yes.

License is not stated in the available content.

Yoink these prompts

Prompt 1
Show me how to run nope_modules to scan my ~/code folder for projects untouched in 6 months.
Prompt 2
Explain how nope_modules decides a project is stale using Git commit history, ignoring generated files.
Prompt 3
Walk me through the two-step scan-then-delete workflow this tool uses to avoid accidental data loss.
Prompt 4
Help me set up nope_modules to run automatically on the first of each month on macOS.

Frequently asked questions

wtf is nope_modules?

A safety-first CLI tool that finds stale, untouched projects and deletes their node_modules folders to free up disk space.

What language is nope_modules written in?

Mainly JavaScript. The stack also includes JavaScript, Node.js, Git.

Is nope_modules actively maintained?

Maintained — commit in last 6 months (last push 2026-05-22).

What license does nope_modules use?

License is not stated in the available content.

How hard is nope_modules to set up?

Setup difficulty is rated easy, with roughly 5min to a first successful run.

Who is nope_modules for?

Mainly developer.

View the repo → Decode another repo

This repo across BitVibe Labs

Don't trust strangers blindly. Verify against the repo.

Other repos in this lane