Find out where Java is installed. Free.
A free, read-only script that lists the Java installations on a machine. You can read it before you run it, it makes no network connections, and nothing leaves your computer.
This is a cut-down version. It is not the JSE-License collection tooling used in a Risk Review, and it is not an Oracle-verified (3PTV) solution. Its output is an indicative inventory only — not a licence position, a compliance report or audit evidence. Please don't send it to Oracle.
A quick look at one machine at a time.
Run it on a Windows or Linux computer and it tells you which Java installations it can find, who published them, which version they are, and whether any are running right now.
What it does
Looks in the usual Java locations, reads each install's release file and file properties
(and the package owner on Linux), notes which installs are running, flags any that are behind Oracle's
latest update or on a release line that no longer gets updates, and writes a CSV and a short summary
to a folder you choose.
What it never does
Makes no network connections, installs nothing, changes no settings, and reads no command lines,
user names or file contents. It collects no CPU, core or virtualisation data, and it only runs Java
if you switch on the optional -VerifyWithJava / --verify option.
| Free discovery script | Java Licensing Risk Review | |
|---|---|---|
| Oracle-verified (3PTV) | No | Yes — with a 3PTV statement |
| Where it runs | One machine at a time, which you run yourself | Your chosen estate, deployed under your change control (SCCM, login scripts, etc.) |
| What it finds | Java installs, vendor, version, running now, and whether each is behind Oracle's latest update | Installs and usage, commercial features, processors/cores and virtualisation data |
| Output | CSV and summary — indicative only | Analyst-checked compliance report you can use in negotiation |
| Safe to use in an audit? | No | Yes — that is what it is built for |
| Help interpreting it | None — free, as-is | Two 45-minute calls: deployment and report walk-through |
Two minutes to set up. Read it first.
Both scripts are plain text with comments. Have your security team read them before you run anything. Neither needs administrator rights, but you will see more if you run them with elevated rights (and your change process allows it). Test on a non-production machine first.
- Unzip the download to a folder, e.g.
C:\Temp\JSE-Discovery. If Windows blocks the files, right-click the zip → Properties → Unblock first. - Open PowerShell in that folder.
- Run it. The bypass applies to this one run only:
Options: -OutputPath, -IncludeUserProfiles, -ExtraPath,
-VerifyWithJava, -Quiet. If your organisation requires signed scripts, run it under your own policy.
- Unzip the download:
- Run it (add
sudofor the fullest view):
Options: -o, -p, --include-home, --verify, -q, --help.
Results are written to a JSE-Discovery-Output folder: one CSV row per Java installation, plus a
summary. Full instructions, the list of what is and isn't collected, and the limitations are in the
README.txt inside each download.
Get the free discovery script.
Tell us who you are and the download unlocks straight away. We use your details only to follow up on this download — there's no newsletter. It's free at any size, though our Risk Review is built for estates of around 500 machines or more.
Thanks — your download is ready.
Remember: this is a cut-down discovery script, not an Oracle-verified solution. Its output is indicative only and shouldn't be sent to Oracle.
Download for Windows Download for LinuxEach zip contains the script and a README.txt with full instructions.
Verify your download
SHA-256 checksums, also published as SHA256SUMS.txt.
On Windows: Get-FileHash .\file.zip. On Linux: sha256sum file.zip.
adf98bd13549dca257b7a9519206c16c81936f1e8d8059ffb4d009d0523329f0
1013e60682640e3da2afecb97eb28b6eb3e668ad783c0ea43ac5ea89d911665c
a7dbd632ad0d169f15d32648a8b78fc22a9876769ce8d68e4d0176bcc9f52da8
d7325599ac2640e3b5a0e3f301523d211a036f86e0a77b98345fd3825d3348e3
Before you run it
Does it send anything to Lime Software?
No. The script makes no network connections and writes only to its output folder. The only data we receive is what you type into the download form on this page. You don't have to send us the script's results.
Is it safe to run?
It only reads: it looks in folders and package information, it doesn't change settings or install anything, and by default it doesn't launch the Java programs it finds. Read the script first, test it on a non-production machine, and run it under your own change control. It is provided as-is, without warranty.
Why isn't this the same as a Risk Review?
A Risk Review uses our Oracle-verified (3PTV) collection tooling, covers usage, commercial features and processor details, and ends with an analyst-checked compliance report. This script gives you a first, indicative inventory of installs on one machine. It can't tell you what you owe, or don't, and it isn't suitable as audit evidence.
Can I run it across thousands of machines?
You can deploy it yourself with your usual tooling and collect the CSVs, but consolidating, interpreting and defending the results at that scale is exactly where a Risk Review helps. For estates of around 500 machines or more, talk to us first.
What does "Oracle-published" in the results mean?
The install reports Oracle as its vendor. Whether it needs a licence depends on the exact version and build, how it is used, and the agreements you hold, so treat it as a prompt to look closer, not a conclusion.
What does the patch-level flag tell me?
Each install is compared with the latest Oracle update for its release line (currently 8u513, 11.0.33.1, 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1, from Oracle's 17 November 2026 update) and marked up to date, behind, or on a release line that no longer gets updates. It's a version comparison only — not a vulnerability assessment, and it doesn't name CVEs. Oracle now releases security updates monthly, so the table inside the script ages quickly; the script warns you when it's more than 45 days old. For non-Oracle builds, “behind” means “check your vendor's latest update”, not “vulnerable”.
Why do some installs show an "Unknown" vendor?
Usually an older install with no release file. Re-running with -VerifyWithJava (Windows) or --verify (Linux) often fills it in, but that option launches the Java program it finds.
Found something worth a closer look?
A Risk Review gives you a report you can act on — Oracle-verified tooling run inside your own network, a fixed fee and no surprises.
