Supply Chain Scanner
Spot supply-chain exposure that leaks your build: published lock files, dependency manifests, build artifacts, and source maps that reveal your whole dependency tree.
Critical3High4Medium19Low16
Critical3 checks
- .env File Exposed at Public URLA .env or .env.local file was found publicly accessible. Environment files contain application secrets, database credentials, API keys, and encryption keys in plaintext.
- PHP Composer auth.json Exposed With Registry CredentialsA Composer auth.json file was found publicly accessible with a live http-basic password or OAuth token, not just placeholder values. This file grants access to private package repositories and, for a GitHub/GitLab token, to the linked account's API.
- npm Install Hook Pipes a Remote Download Into a ShellA publicly accessible package.json has a preinstall, install, or postinstall script that downloads a remote file with curl or wget and pipes it directly into a shell interpreter. This is a known technique used by malicious/compromised npm packages to run arbitrary code the moment the package is installed.
High4 checks
- HTTP Script Loaded on HTTPS PageAn HTTPS page loads a JavaScript file over HTTP. This is a mixed-content violation that allows network attackers to replace the HTTP script with malicious code, compromising the entire HTTPS page.
- Dockerfile or docker-compose.yml ExposedA Dockerfile or docker-compose.yml file was found publicly accessible. These files reveal the base image, environment variables, secrets handling, port mappings, and infrastructure topology.
- Vulnerable Dependency (OSV-Confirmed)A client-side library loaded by this page, at the exact version detected from its script filename, has a published vulnerability in OSV.dev (the Open Source Vulnerabilities database, which aggregates GitHub Security Advisories, npm audit advisories, and other ecosystem-specific sources). See the finding evidence for which library, version, and advisory.
- Import map resolves a module over plain HTTPAn import map on an HTTPS page maps a module specifier to a cleartext http:// URL on a host other than localhost.
Medium19 checks
- npm/yarn Lock File ExposedA package-lock.json or yarn.lock file was found accessible at a public URL. Lock files contain the exact dependency tree including all transitive dependencies and their versions, enabling an attacker to identify vulnerable packages.
- Python Requirements File ExposedA requirements.txt, Pipfile, or Pipfile.lock was found at a public URL. Python dependency files reveal the exact package versions installed, enabling attackers to find known CVEs in your dependencies.
- Ruby Gemfile or Gemfile.lock ExposedA Gemfile or Gemfile.lock was found publicly accessible. Ruby gem dependency files reveal the exact gem versions used, enabling CVE-based vulnerability scanning against your dependencies.
- External CDN Script Without SRI HashAn external JavaScript file is loaded from a CDN without a Subresource Integrity (integrity=) attribute. If the CDN is compromised or serves a different file version, malicious code can run on your site without detection.
- PHP composer.json or composer.lock ExposedA composer.json or composer.lock file was found publicly accessible. PHP Composer dependency files reveal exact package versions including all transitive dependencies.
- CDN Script With No Version Pin and No Integrity HashA script is loaded from jsdelivr's npm alias or unpkg with no version number in the URL (or an explicit @latest) and no integrity attribute. Requesting the same URL tomorrow can return different bytes with nothing to catch the change.
- Rust Cargo.lock ExposedA Cargo.lock file was found publicly accessible. Rust's lock file pins the exact version and source of every crate in the dependency tree, including transitive dependencies not listed in Cargo.toml.
- Go go.sum Checksum File ExposedA go.sum file was found publicly accessible with multiple module checksum entries. This file lists every module in the build, including indirect dependencies, along with the exact version resolved for each.
- Terraform provider lockfile exposedThe response is a .terraform.lock.hcl file: registry.terraform.io provider blocks with their recorded hashes.
- Git dependency with no commit pinA dependency in the exposed manifest resolves from a git source with no commit pin. The value uses git+https, git+ssh, git:// or the github: shorthand, with no 40-character commit hash.
- Import map resolves to an unversioned CDN URLAn import map on this page resolves a bare module specifier to an unversioned CDN URL. The path carries no version at all, or an explicit @latest.
- ES module imported from an unversioned CDN specifierAn import statement pulls a module from a CDN with no version in the specifier. esm.sh, Skypack and esm.run all resolve such a specifier to the newest published release at request time.
- Script loaded from a jsDelivr GitHub branch referenceThe page loads an asset through jsDelivr's GitHub passthrough at a moving reference. The URL carries no @tag at all, or one of @master, @main, @latest or @HEAD.
- Page references RawGit, a shut-down CDNThe page references rawgit.com or cdn.rawgit.com, a CDN that no longer exists. RawGit stopped serving new files in 2018 and shut down completely in October 2019.
- Script loaded from GitHub raw contentA script element on this page loads its source from raw.githubusercontent.com or gist.githubusercontent.com.
- Subresource Integrity hash uses an unsupported algorithmA script or link element carries an integrity attribute with an unrecognised hash prefix. None of its prefixes is sha256, sha384 or sha512, the only algorithms Subresource Integrity defines.
- Cross-origin subresource has integrity but no crossoriginA cross-origin script or stylesheet carries an integrity attribute without a crossorigin attribute. Subresource Integrity requires a CORS-enabled fetch, so the browser cannot check the hash.
- CI workflow definition publicly servedThe response is a CI workflow definition with a jobs block and action steps. That is the shape GitHub Actions and compatible runners use, including runner labels and triggers.
- CI workflow uses a third-party action by mutable tagThe exposed workflow references a third-party action with a tag or branch reference rather than a full commit SHA.
Low16 checks
- Python poetry.lock exposedThe response is a Poetry lockfile: a [[package]] table set with Poetry's own markers. Either its generation banner, or the [metadata] lock-version key that Cargo's identically shaped file does not have.
- Python Pipfile.lock exposedThe response is a Pipenv lockfile, identified by its _meta block and pipfile-spec version.
- Gradle dependency lockfile exposedThe response is a Gradle dependency lockfile, served directly over HTTP. It is identified by Gradle's generated banner, or by lines in the group:artifact:version=configurations form.
- Maven pom.xml exposedThe response is a Maven project object model: a modelVersion of 4.0.0 together with artifact coordinates.
- NuGet package manifest exposedThe response is a NuGet dependency manifest, served directly over HTTP. Either a packages.config with id and version attributes, or a packages.lock.json with resolved versions and content hashes.
- Elixir mix.lock exposedThe response is an Elixir mix.lock file, identified by two or more Hex package tuples in its {:hex, :name, ...} form.
- Dart pubspec.lock exposedThe response is a Dart or Flutter pubspec.lock file, served over HTTP. It is identified by its packages block and the direct main and direct dev markers pub writes.
- Swift Package.resolved exposedThe response is a Swift Package Manager resolution file, served over HTTP. Its pins array carries repository locations and the exact commit revisions the build is pinned to.
- CocoaPods Podfile.lock exposedThe response is a CocoaPods lockfile, identified by its PODS and SPEC CHECKSUMS sections.
- Rust Cargo.toml exposedThe response is a Rust crate manifest: a [package] table with an edition key and a [dependencies] table.
- Go go.mod exposedThe response is a Go module file: a module directive followed by a go language-version directive.
- Python setup.py source exposedThe response is a Python setup.py: a setup() call with an install_requires list.
- Python pyproject.toml exposedThe response is a Python pyproject.toml, served directly over HTTP. It is identified by a [tool.poetry] or [build-system] table, or a [project] table with a requires-python key.
- Asset served directly out of node_modulesA script or stylesheet on this page has a URL containing a /node_modules/ path segment. The dependency directory itself is therefore mapped into the web root.
- Asset loaded from a Bower install directoryA script or stylesheet on this page loads from a bower_components path. Bower was deprecated in 2017 and its registry stopped accepting new packages.
- Software bill of materials publicly servedThe response is a software bill of materials in CycloneDX or SPDX format, listing the components the build shipped.
About the Supply chain checks
- What does the Supply chain category check?
- Spot supply-chain exposure that leaks your build: published lock files, dependency manifests, build artifacts, and source maps that reveal your whole dependency tree. Exposed lock files, dependency manifests, build artifacts, source maps.
- How many supply chain checks are there?
- VulnRadar runs 42 checks in this category, ranging across critical, high, medium, low severity.
- Do I need to install anything to run the supply chain checks?
- No. Paste a URL in the browser or call the REST API, and the scan itself runs from our servers against that URL. There is no agent and no appliance to deploy alongside your application. A browser extension exists if you want to scan the page you are looking at, but nothing has to be installed to use this.
Run the supply chain checks on your site
VulnRadar runs all 42 of these against a URL in seconds, with the evidence and fix for every finding. No agent to install, just paste a URL.