notion-clipper-skill

clawhub:notion-clipper-skill

View source
A
92/100

First Seen

Feb 18, 2026

Last Scanned

Feb 22, 2026

Findings

14

Score

92/100

MEDIUM 1
LOW 13

Findings (14)

MEDIUM
Shell profile modification for persistence
L136

Detects instructions to modify shell config files for environment persistence

add to your ~/.bashrc or ~/.zshrc
FIX

Avoid modifying shell profiles (.bashrc, .zshrc, .profile) programmatically. Instruct users to add PATH entries manually, or use a version manager (nvm, pyenv) instead.

FP?

Likely FP if the match is documentation showing how to add a tool to PATH manually, especially if it only appends to PATH without modifying other settings.

LOW
npx auto-install without confirmation
L31

Detects npx with -y flag that bypasses user confirmation for package installation

npx -y 
FIX

Replace npx -y with an explicit npm install step that pins the package to a specific version, then run it. Remove the -y flag to require user confirmation.

FP?

Likely FP if the npx command runs a well-known, trusted tool (e.g., create-react-app) in documentation context with no version pinning concern.

LOW
npx auto-install without confirmation
L41

Detects npx with -y flag that bypasses user confirmation for package installation

npx -y 
FIX

Replace npx -y with an explicit npm install step that pins the package to a specific version, then run it. Remove the -y flag to require user confirmation.

FP?

Likely FP if the npx command runs a well-known, trusted tool (e.g., create-react-app) in documentation context with no version pinning concern.

LOW
npx auto-install without confirmation
L56

Detects npx with -y flag that bypasses user confirmation for package installation

npx -y 
FIX

Replace npx -y with an explicit npm install step that pins the package to a specific version, then run it. Remove the -y flag to require user confirmation.

FP?

Likely FP if the npx command runs a well-known, trusted tool (e.g., create-react-app) in documentation context with no version pinning concern.

LOW
npx auto-install without confirmation
L59

Detects npx with -y flag that bypasses user confirmation for package installation

npx -y 
FIX

Replace npx -y with an explicit npm install step that pins the package to a specific version, then run it. Remove the -y flag to require user confirmation.

FP?

Likely FP if the npx command runs a well-known, trusted tool (e.g., create-react-app) in documentation context with no version pinning concern.

LOW
npx auto-install without confirmation
L62

Detects npx with -y flag that bypasses user confirmation for package installation

npx -y 
FIX

Replace npx -y with an explicit npm install step that pins the package to a specific version, then run it. Remove the -y flag to require user confirmation.

FP?

Likely FP if the npx command runs a well-known, trusted tool (e.g., create-react-app) in documentation context with no version pinning concern.

LOW
npx auto-install without confirmation
L65

Detects npx with -y flag that bypasses user confirmation for package installation

npx -y 
FIX

Replace npx -y with an explicit npm install step that pins the package to a specific version, then run it. Remove the -y flag to require user confirmation.

FP?

Likely FP if the npx command runs a well-known, trusted tool (e.g., create-react-app) in documentation context with no version pinning concern.

LOW
npx auto-install without confirmation
L68

Detects npx with -y flag that bypasses user confirmation for package installation

npx -y 
FIX

Replace npx -y with an explicit npm install step that pins the package to a specific version, then run it. Remove the -y flag to require user confirmation.

FP?

Likely FP if the npx command runs a well-known, trusted tool (e.g., create-react-app) in documentation context with no version pinning concern.

LOW
npx auto-install without confirmation
L118

Detects npx with -y flag that bypasses user confirmation for package installation

npx -y 
FIX

Replace npx -y with an explicit npm install step that pins the package to a specific version, then run it. Remove the -y flag to require user confirmation.

FP?

Likely FP if the npx command runs a well-known, trusted tool (e.g., create-react-app) in documentation context with no version pinning concern.

LOW
npx auto-install without confirmation
L123

Detects npx with -y flag that bypasses user confirmation for package installation

npx -y 
FIX

Replace npx -y with an explicit npm install step that pins the package to a specific version, then run it. Remove the -y flag to require user confirmation.

FP?

Likely FP if the npx command runs a well-known, trusted tool (e.g., create-react-app) in documentation context with no version pinning concern.

LOW
npx auto-install without confirmation
L128

Detects npx with -y flag that bypasses user confirmation for package installation

npx -y 
FIX

Replace npx -y with an explicit npm install step that pins the package to a specific version, then run it. Remove the -y flag to require user confirmation.

FP?

Likely FP if the npx command runs a well-known, trusted tool (e.g., create-react-app) in documentation context with no version pinning concern.

LOW
npx auto-install without confirmation
L133

Detects npx with -y flag that bypasses user confirmation for package installation

npx -y 
FIX

Replace npx -y with an explicit npm install step that pins the package to a specific version, then run it. Remove the -y flag to require user confirmation.

FP?

Likely FP if the npx command runs a well-known, trusted tool (e.g., create-react-app) in documentation context with no version pinning concern.

LOW
npx auto-install without confirmation
L138

Detects npx with -y flag that bypasses user confirmation for package installation

npx -y 
FIX

Replace npx -y with an explicit npm install step that pins the package to a specific version, then run it. Remove the -y flag to require user confirmation.

FP?

Likely FP if the npx command runs a well-known, trusted tool (e.g., create-react-app) in documentation context with no version pinning concern.

LOW
npx auto-install without confirmation
L181

Detects npx with -y flag that bypasses user confirmation for package installation

npx -y 
FIX

Replace npx -y with an explicit npm install step that pins the package to a specific version, then run it. Remove the -y flag to require user confirmation.

FP?

Likely FP if the npx command runs a well-known, trusted tool (e.g., create-react-app) in documentation context with no version pinning concern.