upgrade - Pensar Apex

The upgrade command checks for and installs the latest version of Pensar Apex.

Syntax

pensar upgrade

Alias: pensar update

Description

The upgrade command:

Checks your current Pensar version
Queries GitHub for the latest release
Downloads and installs the update if available
Verifies the installation

The upgrade process is interactive and will prompt you before making changes.

No Options Required

The upgrade command runs without any flags or options:

pensar upgrade

Or using the alias:

pensar update

Examples

Check for Updates

Run the upgrade command to check for new versions:

pensar upgrade

Output (when update available):

Current version: v0.0.79
Checking for updates...

New version available: v0.0.80

Changelog:
- Fixed SQL injection detection accuracy
- Added support for GraphQL pentesting
- Improved rate limiting handling
- Performance optimizations

Download and install v0.0.80? [Y/n] 

Output (when up to date):

Current version: v0.0.79
Checking for updates...

You are already running the latest version!

Automatic Update

Accept the update prompt to install:

$ pensar upgrade

Current version: v0.0.79
Checking for updates...

New version available: v0.0.80

Download and install v0.0.80? [Y/n] y

→ Downloading pensar v0.0.80...
✓ Downloaded successfully
→ Installing...
✓ Installed successfully
→ Verifying installation...
✓ Verified

Successfully upgraded to v0.0.80!

Run 'pensar version' to verify.

Decline Update

Skip the update by answering ‘n’:

$ pensar upgrade

Current version: v0.0.79
Checking for updates...

New version available: v0.0.80

Download and install v0.0.80? [Y/n] n

Update cancelled.

Using the Alias

The update command works identically:

pensar update

Update Process

The upgrade follows these steps:

Installation Locations

Pensar is installed to different locations based on your installation method:

Shell Script Install
Homebrew
NPM/Yarn
Manual Binary

Default location: ~/.pensar/bin/pensarThe upgrade command updates the binary in place:

~/.pensar/bin/pensar

Make sure this is in your PATH:

export PATH="$HOME/.pensar/bin:$PATH"

Location: Managed by HomebrewIf installed via Homebrew:

brew upgrade pensar

The pensar upgrade command will detect Homebrew and suggest using brew upgrade instead.

Location: Managed by package managerIf installed via npm or yarn:

npm update -g @pensar/apex
# or
yarn global upgrade @pensar/apex

The pensar upgrade command will detect npm/yarn and suggest using the package manager instead.

Location: CustomIf you manually downloaded and placed the binary:

# The upgrade command will attempt to update it in place
# If it fails, download manually:
curl -L https://github.com/pensarai/apex/releases/latest/download/pensar-$(uname -s)-$(uname -m) -o pensar
chmod +x pensar

Version Checking

Check your current version without upgrading:

pensar version
# or
pensar -v
# or
pensar --version

Output:

v0.0.79

Release Channels

Pensar has two release channels:

Stable (Default)

The upgrade command installs stable releases:

pensar upgrade

Stable releases are:

Thoroughly tested
Production-ready
Recommended for most users

Canary (Bleeding Edge)

For the latest features (may be unstable):

# Manual installation required
curl -L https://github.com/pensarai/apex/releases/download/canary/pensar-$(uname -s)-$(uname -m) -o ~/.pensar/bin/pensar
chmod +x ~/.pensar/bin/pensar

Canary releases may contain bugs and breaking changes. Only use for testing or development.

Rollback

If you need to rollback to a previous version:

Method 1: Specific Version

# Download a specific version
curl -L https://github.com/pensarai/apex/releases/download/v0.0.79/pensar-$(uname -s)-$(uname -m) -o ~/.pensar/bin/pensar
chmod +x ~/.pensar/bin/pensar

# Verify
pensar version

Method 2: Previous Version

# List available versions
curl -s https://api.github.com/repos/pensarai/apex/releases | grep '"tag_name"'

# Download desired version
curl -L https://github.com/pensarai/apex/releases/download/v0.0.78/pensar-$(uname -s)-$(uname -m) -o ~/.pensar/bin/pensar
chmod +x ~/.pensar/bin/pensar

Automatic Updates

Pensar checks for updates automatically:

TUI: Shows notification on launch if update available
CLI: Displays update message after command completion

Disable Update Check

To disable automatic update checks:

# Edit config file
vim ~/.pensar/config.json

# Add:
{
  "checkForUpdates": false
}

Update Notifications

When an update is available, you’ll see a notification:

$ pensar pentest --target https://example.com

╭─────────────────────────────────────────────╮
│ Update available: v0.0.80                   │
│ Run 'pensar upgrade' to update              │
╰─────────────────────────────────────────────╯

============================================================
PENTEST ORCHESTRATION
============================================================
...

Exit Codes

Code	Meaning
`0`	Success (updated or already up to date)
`1`	Failure (download failed, installation failed, etc.)

pensar upgrade
echo $?  # Check exit code

Use Cases

Regular Maintenance

Keep Pensar up to date:

# Weekly update check
pensar upgrade

Before Critical Pentests

Ensure you have the latest security improvements:

# Update before important work
pensar upgrade && pensar pentest --target https://example.com

CI/CD Pipeline

Always use the latest version in automation:

#!/bin/bash
set -e

# Install or update Pensar
if command -v pensar &> /dev/null; then
  pensar upgrade
else
  curl -fsSL https://raw.githubusercontent.com/pensarai/apex/main/install.sh | sh
fi

# Run pentest
pensar pentest --target "$TARGET_URL"

Development Testing

Test against the latest version:

# Upgrade to latest
pensar upgrade

# Test your workflow
pensar pentest --target https://staging.example.com

Troubleshooting

Download Fails

If the download fails:

# Check internet connection
ping github.com

# Try manual download
curl -L https://github.com/pensarai/apex/releases/latest/download/pensar-$(uname -s)-$(uname -m) -o /tmp/pensar
chmod +x /tmp/pensar
mv /tmp/pensar ~/.pensar/bin/pensar

Permission Denied

If installation fails with permission errors:

# Check permissions
ls -la ~/.pensar/bin/pensar

# Fix permissions
chmod +x ~/.pensar/bin/pensar

# If directory doesn't exist:
mkdir -p ~/.pensar/bin

Version Not Changing

If pensar version shows old version after upgrade:

# Check which pensar binary is being used
which pensar

# May show system-wide install instead of user install
# Update your PATH:
export PATH="$HOME/.pensar/bin:$PATH"

# Add to shell profile for persistence:
echo 'export PATH="$HOME/.pensar/bin:$PATH"' >> ~/.bashrc
source ~/.bashrc

Network Issues

If you’re behind a proxy or firewall:

# Set proxy environment variables
export HTTP_PROXY="http://proxy.example.com:8080"
export HTTPS_PROXY="http://proxy.example.com:8080"

# Then upgrade
pensar upgrade

Rate Limiting

GitHub API rate limits may affect update checks:

# Check rate limit status
curl -s https://api.github.com/rate_limit

# Wait an hour or authenticate with GitHub token
export GITHUB_TOKEN="your-token-here"
pensar upgrade

Configuration

Upgrade behavior can be configured in ~/.pensar/config.json:

{
  "updates": {
    "checkForUpdates": true,
    "autoDownload": false,
    "channel": "stable",
    "notifyOnLaunch": true
  }
}

checkForUpdates

boolean

default:"true"

Enable automatic update checking

autoDownload

boolean

default:"false"

Automatically download updates (still requires confirmation to install)

channel

string

default:"stable"

Release channel: stable or canary

notifyOnLaunch

boolean

default:"true"

Show update notifications when launching Pensar

doctor - Verify system configuration after upgrade
pensar - Launch TUI with updated version
version - Check current version

Next Steps

Changelog

View all release notes and changes

GitHub Releases

Download specific versions manually

Get Started

Core Concepts

Command Reference

Configuration

Guides

Security

​Syntax

​Description

​No Options Required

​Examples

​Check for Updates

​Automatic Update

​Decline Update

​Using the Alias

​Update Process

​Installation Locations

​Version Checking

​Release Channels

​Stable (Default)

​Canary (Bleeding Edge)

​Rollback

​Method 1: Specific Version

​Method 2: Previous Version

​Automatic Updates

​Disable Update Check

​Update Notifications

​Exit Codes

​Use Cases

​Regular Maintenance

​Before Critical Pentests

​CI/CD Pipeline

​Development Testing

​Troubleshooting

​Download Fails

​Permission Denied

​Version Not Changing

​Network Issues

​Rate Limiting

​Configuration

​Related Commands

​Next Steps

Changelog

GitHub Releases

Build docs developers (and LLMs) love

Syntax

Description

No Options Required

Examples

Check for Updates

Automatic Update

Decline Update

Using the Alias

Update Process

Installation Locations

Version Checking

Release Channels

Stable (Default)

Canary (Bleeding Edge)

Rollback

Method 1: Specific Version

Method 2: Previous Version

Automatic Updates

Disable Update Check

Update Notifications

Exit Codes

Use Cases

Regular Maintenance

Before Critical Pentests

CI/CD Pipeline

Development Testing

Troubleshooting

Download Fails

Permission Denied

Version Not Changing

Network Issues

Rate Limiting

Configuration

Related Commands

Next Steps