Gathering detailed insights and metrics for clear-npx-cache
Gathering detailed insights and metrics for clear-npx-cache
Gathering detailed insights and metrics for clear-npx-cache
Gathering detailed insights and metrics for clear-npx-cache
npm install clear-npx-cache
Typescript
Module System
Node Version
NPM Version
TypeScript (94.67%)
JavaScript (5.33%)
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
42 Stars
21 Commits
3 Forks
2 Watchers
1 Branches
3 Contributors
Updated on Feb 02, 2025
Latest Version
1.1.2
Package Id
clear-npx-cache@1.1.2
Unpacked Size
4.09 kB
Size
1.91 kB
File Count
5
NPM Version
9.6.7
Node Version
18.17.1
Published on
Oct 26, 2023
Cumulative downloads
Total Downloads
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
1
4
NPX has a bug. When you call, for example, one of this:
1npx create-react-app
1npx cowsay "I'm a cow!"
…then you will do it successfully. But NPX will install it to your NPX cache, and NPX will not be watching lifetime of its cache. NPX package will be stored in the cache forever. When NPX-utility was updated, the cache will not be updated. I'll repeat, it's a bug.
If you sometimes use a NPX-utility, you will store an old version of this package in your cache. And every package update will not be seen by NPX. Cache clearing will solve this trouble.
If you are developing a new NPX-package, you will test it. But you can publish a bugful package, and after a fix and re-publishing you will see same bug. I don't want you repeating my expirience in bug-finding and source-code-jumping.
1npx clear-npx-cache
Expected behavior:
npm config get cache
)_npx
_npx
directoryNo vulnerabilities found.
Reason
no binaries found in the repo
Reason
0 existing vulnerabilities detected
Reason
Found 1/20 approved changesets -- score normalized to 0
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
Reason
license file not detected
Details
Reason
project is not fuzzed
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Score
Last Scanned on 2025-07-07
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More