<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>Penthera news</title>
  <id>https://penthera.org/news</id>
  <link rel="alternate" type="text/html" href="https://penthera.org/news"/>
  <link rel="self" type="application/atom+xml" href="https://penthera.org/news/feed.xml"/>
  <updated>2026-11-01T00:00:00Z</updated>
  <entry><title>Penthera 2.2.0</title><id>https://github.com/danoszz/penthera/releases/tag/v2.2.0</id><link href="https://github.com/danoszz/penthera/releases/tag/v2.2.0"/><updated>2026-11-01T00:00:00Z</updated><summary>What changed, in the changelog.</summary></entry>
  <entry><title>Penthera 2.1.2</title><id>https://github.com/danoszz/penthera/releases/tag/v2.1.2</id><link href="https://github.com/danoszz/penthera/releases/tag/v2.1.2"/><updated>2026-10-31T00:00:00Z</updated><summary>What changed, in the changelog.</summary></entry>
  <entry><title>State of the Web 2026, follow-up: is the front-door gap real, and what do bot challenges hide?</title><id>https://github.com/danoszz/penthera/blob/main/docs/research/prereg/E20r-front-door-replication.md</id><link href="https://github.com/danoszz/penthera/blob/main/docs/research/prereg/E20r-front-door-replication.md"/><updated>2026-10-30T00:00:00Z</updated><summary>A follow-up with new groups of sites and a new check, registered before it ran. Aggregates only.</summary></entry>
  <entry><title>Penthera 2.1.1</title><id>https://github.com/danoszz/penthera/releases/tag/v2.1.1</id><link href="https://github.com/danoszz/penthera/releases/tag/v2.1.1"/><updated>2026-10-30T00:00:00Z</updated><summary>What changed, in the changelog.</summary></entry>
  <entry><title>State of the Web 2026: how do websites score on front-door checks?</title><id>https://github.com/danoszz/penthera/blob/main/docs/research/prereg/E20-front-door.md</id><link href="https://github.com/danoszz/penthera/blob/main/docs/research/prereg/E20-front-door.md"/><updated>2026-10-29T00:00:00Z</updated><summary>How do the most visited sites, and recent startups, score on the live check's passive front-door checks? Aggregates only.</summary></entry>
  <entry><title>Penthera 2.1.0</title><id>https://github.com/danoszz/penthera/releases/tag/v2.1.0</id><link href="https://github.com/danoszz/penthera/releases/tag/v2.1.0"/><updated>2026-10-29T00:00:00Z</updated><summary>What changed, in the changelog.</summary></entry>
  <entry><title>E17: the registered run on macOS and Ubuntu made no outside connection and gave the same result, for every command in scope</title><id>https://github.com/danoszz/penthera/blob/main/docs/research/prereg/E17-offline-and-determinism.md</id><link href="https://github.com/danoszz/penthera/blob/main/docs/research/prereg/E17-offline-and-determinism.md"/><updated>2026-10-28T00:00:00Z</updated><summary>URL scans are covered only with --offline: without it, a URL scan downloads the Retire.js database. git runs outside the guard.</summary></entry>
  <entry><title>How we benchmarked Penthera against 25 free tools, losses included</title><id>https://penthera.org/blog/sealed-half-benchmark</id><link href="https://penthera.org/blog/sealed-half-benchmark"/><updated>2026-10-28T00:00:00Z</updated><summary>We tuned on one half of four public datasets and scored once on the other, sealed half. What that method is, what it found, and how far to trust it.</summary></entry>
  <entry><title>We benchmarked 10 free secret scanners on 2,220 labelled secrets. We came 2nd.</title><id>https://penthera.org/blog/secret-scanners-creddata</id><link href="https://penthera.org/blog/secret-scanners-creddata"/><updated>2026-10-28T00:00:00Z</updated><summary>gitleaks, trufflehog, deepsecrets, Nosey Parker and five more on Samsung CredData's sealed half, with intervals, the limits, and where Penthera loses.</summary></entry>
  <entry><title>E14: merging the free tools found more secrets but cost more than 0.02 precision, so --giants keeps Penthera-first</title><id>https://github.com/danoszz/penthera/blob/main/docs/research/prereg/E14-giants-combination.md</id><link href="https://github.com/danoszz/penthera/blob/main/docs/research/prereg/E14-giants-combination.md"/><updated>2026-10-25T00:00:00Z</updated><summary>Does one report from Penthera and the free tools find more than Penthera alone, without losing more than a fixed margin of precision? The answer sets the default for --giants.</summary></entry>
  <entry><title>Leaked secrets</title><id>https://penthera.org/benchmarks/secrets</id><link href="https://penthera.org/benchmarks/secrets"/><updated>2026-10-25T00:00:00Z</updated><summary>Every tool, every interval, on the sealed half.</summary></entry>
  <entry><title>Malicious npm packages</title><id>https://penthera.org/benchmarks/npm-malware</id><link href="https://penthera.org/benchmarks/npm-malware"/><updated>2026-10-25T00:00:00Z</updated><summary>Every tool, every interval, on the sealed half.</summary></entry>
  <entry><title>Malicious PyPI packages</title><id>https://penthera.org/benchmarks/pypi-malware</id><link href="https://penthera.org/benchmarks/pypi-malware"/><updated>2026-10-25T00:00:00Z</updated><summary>Every tool, every interval, on the sealed half.</summary></entry>
  <entry><title>Injection bugs in JavaScript libraries</title><id>https://penthera.org/benchmarks/js-injection</id><link href="https://penthera.org/benchmarks/js-injection"/><updated>2026-10-25T00:00:00Z</updated><summary>Every tool, every interval, on the sealed half.</summary></entry>
  <entry><title>Penthera 2.0.0</title><id>https://github.com/danoszz/penthera/releases/tag/v2.0.0</id><link href="https://github.com/danoszz/penthera/releases/tag/v2.0.0"/><updated>2026-10-25T00:00:00Z</updated><summary>What changed, in the changelog.</summary></entry>
  <entry><title>E11: Penthera 1.9.0 missed all five registered targets on the three public datasets</title><id>https://github.com/danoszz/penthera/blob/main/docs/research/prereg/E11-public-benchmarks.md</id><link href="https://github.com/danoszz/penthera/blob/main/docs/research/prereg/E11-public-benchmarks.md"/><updated>2026-10-24T00:00:00Z</updated><summary>One public benchmark per capability, with answer keys we had no hand in: secrets on Samsung CredData, code sinks on SecBench.js, malicious packages on DataDog's dataset.</summary></entry>
  <entry><title>E11b: 2nd on secrets, tied 1st to 3rd on npm and PyPI malware, tied 1st to 4th on JS injection</title><id>https://github.com/danoszz/penthera/blob/main/docs/research/prereg/E11b-improvement-study.md</id><link href="https://github.com/danoszz/penthera/blob/main/docs/research/prereg/E11b-improvement-study.md"/><updated>2026-10-24T00:00:00Z</updated><summary>Tune on a dev half, then score a sealed test half once. Only the test half's numbers are published as the after.</summary></entry>
  <entry><title>Penthera 1.9.0</title><id>https://github.com/danoszz/penthera/releases/tag/v1.9.0</id><link href="https://github.com/danoszz/penthera/releases/tag/v1.9.0"/><updated>2026-10-23T00:00:00Z</updated><summary>What changed, in the changelog.</summary></entry>
  <entry><title>eMudhra's broken CA keys show in the public key, and the TLS check now looks for them</title><id>https://github.com/danoszz/penthera/blob/main/docs/research/emudhra-weak-keys-2026-10.md</id><link href="https://github.com/danoszz/penthera/blob/main/docs/research/emudhra-weak-keys-2026-10.md"/><updated>2026-10-22T00:00:00Z</updated><summary>Each private key was an integer below 256, so a passive handshake is enough to find it. A match is proof, so the finding is confirmed.</summary></entry>
  <entry><title>GitLab's critical patch: a passive scan cannot read a self-managed GitLab's version</title><id>https://github.com/danoszz/penthera/blob/main/docs/research/gitlab-version-exposure-2026-10.md</id><link href="https://github.com/danoszz/penthera/blob/main/docs/research/gitlab-version-exposure-2026-10.md"/><updated>2026-10-22T00:00:00Z</updated><summary>Asset fingerprinting is ruled out. The note proposes a rule that reads the version from the repository instead; no rule shipped.</summary></entry>
  <entry><title>PHP's 21 Oct flaws: Penthera checks the version a site shows, and says when it cannot tell</title><id>https://github.com/danoszz/penthera/blob/main/docs/research/case-study-php-2026-10.md</id><link href="https://github.com/danoszz/penthera/blob/main/docs/research/case-study-php-2026-10.md"/><updated>2026-10-21T00:00:00Z</updated><summary>Released in 1.8.0. A hidden version is never reported as safe, and the fixed versions match the ones in OpenAI's own checker.</summary></entry>
  <entry><title>E1: Penthera's accuracy on real code</title><id>https://github.com/danoszz/penthera/blob/main/docs/research/prereg/E1-real-world-accuracy.md</id><link href="https://github.com/danoszz/penthera/blob/main/docs/research/prereg/E1-real-world-accuracy.md"/><updated>2026-10-20T00:00:00Z</updated><summary>How accurate is Penthera's static analysis on real web apps and agent setups its authors did not write? Precision and recall per category, each with a 95% interval.</summary></entry>
  <entry><title>2026 agent incidents: six gaps for Penthera, from verifier integrity to agent sandboxes</title><id>https://github.com/danoszz/penthera/blob/main/docs/research/agent-incidents-2026.md</id><link href="https://github.com/danoszz/penthera/blob/main/docs/research/agent-incidents-2026.md"/><updated>2026-10-20T00:00:00Z</updated><summary>Agents under evaluation reached real systems they were never meant to touch. Each lesson ends in an action, and the draft study E8 tests one of them.</summary></entry>
</feed>
