TreeMap
A free, open-source disk-space visualizer. Squarified treemap, duplicate hunting, disk-full forecasting, and cleanup that only ever moves files to the Trash.
翻译准备中
PDF Seal is a free, open-source PDF workspace. Manage signature fields, inspect document metadata, browse and compare revision history, and share PDFs securely — all in your browser, with nothing stored on a server.
翻译准备中
取自仓库 README
正在加载完整 README。 以下为已保存的摘录。
pdf-seal is a browser-based PDF signature field editor built with Node.js, Express, TypeScript, and pdf-lib. It helps you upload a PDF, place signature fields directly on the document, adjust their size and position, and save the updated file.
The app opens as a web workspace with two main areas:
• A document viewer on the left where you can preview the PDF, move between pages, and zoom in or out.
• A control panel on the right where you can add and edit signature fields.查看完整 README ↗A browser-based editor for preparing PDFs for signing. Upload a PDF, place signature fields, then download it or share it with someone else.
PDF Seal does not sign PDFs cryptographically. It adds signature form fields that PDF viewers and e-signing tools recognise, and it can inspect signatures that already exist.
| Section | What it does |
|---|---|
| Overview | Read-only summary of the document: metadata (title, author…), fields, signatures, stamps, links and comments. |
| Signatures | Place, move, resize and remove signature fields, and save them as reusable templates. |
| Versions | Local history of every upload and edit. Compare any two versions and see what changed. |
| Certificates | Inspect the certificate chain of existing signatures and run an optional trust check. |
Also: Share sends the PDF directly to another browser (WebRTC), ? opens help and an interactive tour, and a browser extension can send PDFs from any page into the app.
app/ Angular UI
server/ Express API (+ its tests and scripts)
extension/ Chromium browser extension
All three share the single package.json at the root.
Requires Node.js 24 (nvm use picks it up from .nvmrc; ^22.22.3 and 26+ also work).
npm install
npm run dev # develop at http://localhost:3000 with live reload
npm run build # build server + UI into dist/
npm start # run the built app at http://localhost:3000
npm test # unit tests (server + Angular); no running server needed
npm run test:e2e # end-to-end tests in Chromium (builds the app first)
The Angular unit tests run in jsdom with every server call mocked, so they work anywhere, CI included. The e2e tests (e2e/, Playwright) build and start the app themselves and drive it in a real browser; the first run also downloads Playwright's Chromium. On Linux, if Chromium then fails to launch, install its system libraries with npx playwright install-deps chromium.
Or with Docker:
docker compose up --build
More commands (coverage, demo sample, extension packaging) are listed in package.json; contributor notes are in AGENTS.md.
Documents are processed in memory and deleted after each request. See PRIVACY_POLICY.md.