080073a7d7
Checks npm prefix ownership, PATH wiring, cache ownership, shell history for sudo npm usage, and n/nvm version manager config. Runs daily at 08:10 via cron and on initial setup.sh run. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Security Tools
A collection of security scripts versioned in this repository.
Claude Code Context
This project is maintained with Claude Code. The working directory on macOS is:
/Users/petermarfleet/code/bin/security
To resume work in Claude Code from this directory:
cd /Users/petermarfleet/code/bin/security
claude
Cloning to a New Machine
If git is not installed (e.g. a fresh LXC/VM):
apt install git -y
Then clone and run setup:
On Tailscale:
git clone http://100.120.125.113:3000/pdm/security-tools.git
cd security-tools
bash setup.sh
Without Tailscale:
git clone https://gitea.pdmarf.co.uk/pdm/security-tools.git
cd security-tools
bash setup.sh
To clone to a specific path:
git clone http://100.120.125.113:3000/pdm/security-tools.git /path/to/destination
Activating on a New VM
After cloning, run setup.sh once. It will:
- Ask for your Telegram bot token and chat ID
- Register cron jobs to run scans daily at 08:00
- Send a test Telegram message confirming the VM is active
- Create a
logs/folder — logs are kept for 60 days then auto-deleted
Updating an Existing VM
When changes are pushed to this repo, update any VM by running:
cd ~/security-tools
git pull
bash setup.sh
setup.sh is safe to re-run — it skips steps already completed.