League SoftwaresSECURITY

BUILT FOR AI-WRITTEN CODE

Ship with
confidence.
Know what
needs fixing.

AI helps you ship faster, and it ships small mistakes just as fast: exposed keys, unchecked input, outdated packages. Those are exactly the gaps attackers look for. Scan your website or code free, then get clear fixes.

1 free scan per email · No code execution · Practical findings

league-scan · free check

Example output above. Type your own address to start a free check.

  • HTTPS and TLS
  • Security headers
  • Exposed .env and .git files
  • Cookie flags
  • Secrets in code
  • SQL and command injection
  • Vulnerable dependencies
  • Open API descriptions
  • AI provenance signals
  • Swift, Objective-C and C rules
  • Supabase keys and Row Level Security
  • Payment webhooks and prices
  • Login rate limits and roles

THREE WAYS TO LOOK CLOSER

Less uncertainty.
More direction.

Start with an automated check. Bring the findings to your team, or work with us on a deeper review.

01 / WEBSITE

Check your public surface.

See how your website handles HTTPS, security headers, cookies, insecure resources, exposed files and public API descriptions.

  • Crawls up to 15 public pages
  • Exposed files, open API docs and bot controls
  • Bounded, non-invasive requests
Scan a website

02 / SOURCE CODE

Catch patterns worth fixing.

Upload a source ZIP to find exposed secrets, injection flaws, unsafe code patterns, risky configuration and known dependency advisories.

  • File and line references
  • Optional dependency lookup
  • No installation or code execution
Review your code

03 / AI PROVENANCE

Look for evidence. Not a score.

Inspect builder metadata, integrations and explicit AI attribution in a website or uploaded source.

  • Included in both checks
  • Signals linked to their location
  • No invented “AI-generated” percentage
Understand the evidence

START WITH WHAT YOU HAVE

A URL.
A codebase.
A clearer next step.

Choose a check and get a report in your browser. Save a copy, share it with your developer, or use it to start a deeper conversation.

Designed to keep things private. No uploaded source or reports are saved on our server. Download your report before leaving the page.

Data handling & coverage

Start with your website.

We’ll crawl up to 15 public pages by following links on your site, and inspect each response. AI provenance signals are included.

Public pages on one site only. No login, form submission or exploit testing. robots.txt is honoured.

FROM A QUESTION TO A PLAN

Simple to start.
Useful to act on.

Read our methodology
01

Choose your check.

Enter a public URL or upload a ZIP of the code you’re authorized to review.

02

Understand the findings.

See observations and review candidates, with priorities, locations and practical fixes.

03

Make the next move.

Download the report, validate it with your team and address what matters to your application.

GOOD QUESTIONS

Know what
you’re getting.

What does the security score mean?

It starts at 100 and deducts a fixed amount for each finding, by priority. It summarises the automated checks that ran on the pages we could reach. It is not a certification and a high score does not mean a website or codebase is secure.

Is this a full penetration test?

No. Website scans crawl a limited number of public pages and inspect their responses. Code reviews identify patterns and optional dependency matches. Login flows, access control, business logic and exploitability require a separately scoped review.

Can you prove that a website was built with AI?

No. We look for explicit attribution, generator metadata and builder integrations. These are evidence signals with limitations. A result of “inconclusive” is valid; missing signals do not prove human authorship.

What happens to my code?

We don’t keep it. A ZIP upload or a repository snapshot is read in memory, never extracted to disk or run, and discarded when the scan finishes. Reports are returned to your browser and not saved on our server. For a private repository, the access token is used only to download that one copy and is never stored or logged; use a read-only token that expires soon and revoke it afterwards. Optional OSV lookups send package names and versions only. Read the details.

Can League Softwares help fix the issues?

Yes. Contact us with your report to discuss remediation, a manual code review or a broader application assessment. Scope and pricing are agreed before work starts.

A PARTNER BEYOND THE REPORT

Let’s make your
next release stronger.

Talk to League Softwares