Resource leak in JarAnalyzer constructor if entries.sort() throws

In `JarAnalyzer.java`, the constructor opens a `JarFile` and then sorts entries:

```java
List entries = Collections.list(jarFile.entries());
entries.sort(Comparator.comparing(ZipEntry::getName)); // NPE if entry has null name
```

If any `JarEntry` has a `null` name (possible in malformed ZIPs), `Comparator.comparing` throws NPE before the `getManifest()` try/catch block is reached. The `JarFile` handle is never closed, causing a resource leak.

**Fix**: Either validate entry names before sorting, or use a null-safe comparator:
```java
entries.sort(Comparator.comparing(ZipEntry::getName, Comparator.nullsLast(Comparator.naturalOrder())));
```

Start in JarAnalyzer.java at the constructor, where entries are collected and sorted before the getManifest() try/catch block. Inspect how malformed entries with null names are handled and whether the existing test suite covers this path. Done means sorting cannot bypass JarFile cleanup when an entry name causes an exception.

Written by the indexing model from the issue text.