How adityasinha-1988/cse2221-cryptography works
This repository is a static, client-side educational web portal (GitHub Pages) for experimenting with classical cryptography. There is no backend/service layer and (based on the tree) no explicit build system—just HTML pages that run JavaScript in the browser.
So the “system” you’re diagramming is primarily:
• Browser UI + JS cipher logic
• Navigation between module pages
• Any client-side-only data flows (plaintext → algorithm → ciphertext; optional analysis)
File tree analysis (what components exist)
Top-level files are individual modules/pages:
• index.html — the Dashboard / main menu
• Vigenere.html — Vigenère cipher module
• Hill.html — Hill cipher module
• Play.html — Playfair cipher module
• tranpost_railfence.html — Rail Fence (transposition) module
• Attacks.html — Cryptanalysis / attacks (frequency analysis, brute force, etc.)
• Randomness.html — randomness-related lab page (likely demonstrating randomness tests or key/material generation concepts)
Notably absent (in the provided tree):
• Separate /js, /css, /assets folders. This implies the JS/CSS might be inline in each HTML file or loaded from CDNs.
• Any server code, DB, API routes, authentication, storage.
README signals (architecture + runtime model)
README confirms:
• HTML/CSS/JS (ES6) only
• “single-page portal” in the sense of a dashboard hub, but the tree indicates it’s really a multi-page static site with a consistent navigation pattern (“Back to Dashboard”).
• Modules are interactive cipher demos + cryptanalysis tools.
Component (per page): UI Controls, Validation, Algorithm Core, Visualization/Output
• Hill.html (matrix operations / modular inverse)
• Attacks.html (analysis pipelines)
That yields maximum detail without overthinking, and it captures the essential architecture of this specific project.