robinmoisson/staticrypt

Password protect a static HTML page, decrypted in-browser in JS with no dependency. No server logic needed.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 40 minutes ago
Added to GitGenius on September 8th, 2026
Created on April 29th, 2017
Open Issues & Pull Requests: 33 (+0)
GitHub issues: Enabled
Number of forks: 495
Total Stargazers: 8,031 (+0)
Total Subscribers: 54 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 24.6 hours
Mean response time: 7.5 days
90th percentile: 20.7 days
Tracked items: 12

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 18
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 403 days
Stale 30+ days: 18
Stale 90+ days: 18

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (8)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

StatiCrypt is a command-line tool and browser-based utility that password-protects static HTML pages with client-side decryption and no server backend required.

The tool solves the problem of securing sensitive content on static hosting platforms like GitHub Pages or Netlify, where server-side authentication is unavailable. It encrypts HTML files using AES-256 and the WebCrypto API, producing a static HTML page with an embedded password prompt. Visitors enter the password in their browser, and decryption happens entirely client-side in JavaScript with no dependencies, meaning the encrypted file can be safely hosted anywhere.

StatiCrypt suits developers who need to password-protect individual HTML documents or entire static sites without infrastructure overhead. It works well for sharing sensitive documents, private documentation, or restricted content via static hosting. The tool offers both a web-based encryption interface for one-off use and a CLI for automation in build processes. Users can encrypt single files, batch-process directories, or generate shareable auto-decrypt links. The project notes that v3 requires HTTPS or localhost contexts due to WebCrypto availability; those needing HTTP support should use v2.

Development activity shows consistent maintenance with regular updates addressing user needs. The maintainer actively responds to issues and implements feature requests. The project includes clear migration documentation when significant changes occur. Documentation is thorough, covering CLI usage, configuration options, and technical implementation details. The codebase remains focused on its core encryption functionality without scope creep.