Fossary314CatalogEN
Fully verified40,962

Development

IT Tools

IT Tools collects text encoders, hash calculators and format converters in one self-hosted browser interface. This static, non-root recipe serves the pinned upstream build without an application database; configuration backups do not include favorites or tool data stored in each browser.

GPL-3.0-onlyVersion 2024.10.22-7ca5933
Download ComposeOpen in editorDownload .env.exampleGenerator

Overview

IT Tools

A private browser toolbox for development: Unicode encoding, hashes, data formats and other small operations. This recipe serves the official static build without a database or user accounts. The pinned version has no Russian interface; Russian screenshots show the native English UI with original Russian sample data.

Favorites, theme, language and some tool inputs live in browser storage. The server has no copy. Moving machines or clearing the site needs a separately retained browser profile if you want those preferences back.

The latest stable release is dated 2024-10-22; no newer stable release was found on 2026-10-25. The image is pinned; this does not promise current dependencies. Browser smoke verifies Unicode Base64 roundtrip, SHA-256, JSON-to-YAML and invalid JSON rejection without off-origin requests in those scenarios.

Configuration assessment (2026-10-25): loopback, UID 101, read-only root, no capabilities and no persistent application volume. Authentication is not built in. Image vulnerabilities were not scanned. Avoid production secrets in a shared browser. VITE configuration is baked at build time and cannot be changed through runtime env.

Update tracking

These are stored results of separate checks, not real-time data. An unknown status means the check has not been performed yet.

New releases

Recipe version compared with the latest known upstream release. A version number, not a reading of what changed.

Current version 2024.10.22-7ca5933Oct 25, 2026, 8:23 AM UTC

Critical vulnerabilities

Result of a dedicated Docker image scan, not a Compose configuration check.

Not checkedNot checked

Breaking updates

A new major version is found by comparing version numbers. A compatibility verdict is entered by hand after reading the release notes and the migration steps.

Not checkedNot checked

compose.yaml

Upstream Compose changes relative to the verified recipe.

Upstream Compose is not trackedNot checked

Outdated Docker images

Pinned image tags checked for newer versions.

Not checkedNot checked

From observation to action

Update plan

The recipe already pins the latest known release. The steps below show the evidence retained for that version.

2024.10.22-7ca59332024.10.22-7ca5933

  1. Open the release evidence

    Open this release on GitHub ↗ The link is evidence to review, not proof of compatibility.

  2. Review the version boundary

    The version numbers do not cross a major compatibility boundary. No compatibility verdict has been recorded.

  3. Prepare image-tag changes

    No image-tag change is currently planned.

  4. Follow the documented migration shape

    Change the tag and restart. Release-specific migration steps still come from the release notes and installation guide.

  5. Protect the rollback point

    No version change is currently planned. The recipe includes a backup procedure. Restore has been tested.

  6. Verify the updated recipe

    An exact Fully verified check for this target was recorded on 2026-10-25.

Read the update procedure in the installation guide ↓

Specifications

Project and licenses

Project status
Active
Editorial verdict
Experimental
GitHub Stars
40,962
Latest release
2024-10-22
Releases per year
0
Implementation languages
TypeScript
Application license
GPL-3.0-only
Recipe license
MIT
License restrictions
No additional restrictions

Clients and localization

Web
Yes
Android
No
iOS
No
Desktop
No
Interface languages
English, German, Spanish, French, Portuguese, Ukrainian, Vietnamese, Chinese
Documentation languages
English, Russian

Operations

Maintenance difficulty
Very easy
Backup
Yes
Restore tested
Yes
Healthcheck
Yes
Reverse proxy required
No
Database
No database
Update complexity
Change the tag and restart

Access and accounts

OIDC
Not supported
SAML
Not supported
Two-factor authentication
Not supported
Reverse proxy header auth
No

Recipe verification

amd64
Passed
arm64
Not tested
Recipe version
1
Image
ghcr.io/corentinth/it-tools
Page updated
2026-10-25

On amd64, verifies non-root/read-only serving, SPA routes, native browser Unicode Base64 roundtrip, SHA-256, JSON-to-YAML and invalid-input validation without off-origin requests for those tools. Recreates a clean deployment, restores a custom Nginx configuration marker, rejects incomplete archives before mutation, and preserves stopped-state backup. ARM64 was not tested. Backups cover server configuration, environment and Compose only. Favorites, preferences and any persisted tool inputs belong to browser storage and are not server-restored. Other tools, external links, TLS proxies, authentication gateways and dependency vulnerabilities were not exercised or scanned.

Check historyVersions, architectures, smoke and restore results

Security and exposure

Security assessment
Warnings found
Assessed
2026-10-25
Public exposure
Supported
Default bind
Localhost only
Privileged
No
Host network
No
Docker socket
No
Known risks:
  • This static application has no accounts, native OIDC, MFA or authorization. Anyone who can reach it can use it. Keep the recipe on loopback; use a private VPN or an independently protected HTTPS gateway if needed.
  • Some tool values and favorites persist in browser local storage; clearing the site or losing the browser profile loses them. Server backups cannot recover browser data. Do not paste production keys or untrusted active content into casual utility sessions; browser extensions and shared profiles can observe your input.
  • The latest stable upstream image is dated 2024-10-22, verified on 2026-10-25. A successful smoke does not establish current dependency security or ongoing release maintenance. No vulnerability scan is claimed.
  • The tested encoders, hashing and format conversions run in the browser without off-origin requests. This is a scoped observation, not a guarantee for every tool, external link or future image. Frontend VITE settings are build-time; runtime environment variables do not rebuild the official image.

Installation levels

The status shows how fully the published recipe meets each level's requirements.

Ready

For home

A minimal setup for a local network or access through a VPN.

  • Single server
  • Local access
  • Minimum components

The recipe covers every requirement at this level.

Ready

For a VPS

A public deployment with protected access and backups.

  • Domain
  • HTTPS via reverse proxy
  • Off-server backup

The recipe covers every requirement at this level.

Not supported

Reliable

A setup designed for predictable operations and observability.

  • Separate database
  • Healthcheck
  • External monitoring
  • CPU and memory limits

You still need to add: separate database, external monitoring, cpu and memory limits.

Tailored to your server

Configuration generator

Answer five questions and download a ready-to-run IT Tools bundle.

Runs locally
01 Do you have a domain?
02 Which reverse proxy?
03 Server architecture
04 Where should data be stored?

Use an absolute path for a separate disk, such as /srv/it-tools.

05 Is VPN access required?

Your bundle is ready

The archive is created in your browser. Your answers are never sent anywhere.

The same files as one shell script, written in plain heredocs so you can read the whole thing before it runs. It checks Docker, the architecture, memory, disk and the ports it needs, and writes nothing until you add --apply.

Screenshots

Quick start

Read the full guide first: it explains external access, backups, and data locations.

Prepare settingscp .env.example .env
Launchdocker compose up -d
Check statusdocker compose ps

Step-by-step guide

Install IT Tools

Requires Docker Engine, Compose >=2.24, 1 CPU, 128 MB RAM (256 MB recommended) and 1 GB disk for the image. Tested on amd64; the image also publishes arm64.

cp .env.example .env
docker compose up -d --wait

Open http://127.0.0.1:8084. There is no login. For a remote server use ssh -L 8084:127.0.0.1:8084 user@server.

Environment

  • IT_TOOLS_VERSION: explicit official tag 2024.10.22-7ca5933.
  • IT_TOOLS_PORT: loopback HTTP port, initially 8084.
  • IT_TOOLS_BACKUP_DIR: optional backup directory, otherwise ./backups.

config/nginx.conf sets unprivileged container port 8080 and temporary files under /tmp. UID 101 reads it without write access. The application is static: runtime VITE variables do not change the build.

VPS

Keep the port firewalled on a VPS. Use an SSH tunnel, VPN or separately protected HTTPS gateway.

LAN / VPN

Use a tunnel or VPN proxy for home access. Publishing the interface grants use to everyone the network permits; there are no accounts.

HTTPS

Set DNS and configure one proxy sample below. Keep the recipe on loopback; HTTPS alone does not add login.

Caddy

Set the domain and port in proxy/Caddyfile. The sample assumes host-based Caddy with automatic TLS.

Nginx

Set the domain, port and TLS certificate paths in proxy/nginx.conf. This external proxy is separate from the static server in the container.

Traefik

Load proxy/traefik.yaml through a file provider, with websecure and letsencrypt. A containerized proxy needs separate networking; its loopback does not reach the host.

Data / Данные

The server holds only env, Compose and config/nginx.conf. Favorites, language, theme and some tool inputs are in browser local storage. Server backup is not browser-data backup.

Backup

Run ./backup.sh. It archives config, env and Compose without stopping the static server. Keep an off-server copy; encrypt it if you added secrets. Retain the browser profile separately.

Restore / Восстановление

./restore.sh backups/it-tools-TIMESTAMP.tar.gz validates the archive and Nginx syntax before replacement, makes a safety backup and starts the server with restored config. Use trusted archives and the matching version. Env/Compose are not activated automatically: compare them manually. Browser data is not restored.

Update / Обновление

Review release notes, back up configuration, set an explicit tag and run docker compose pull && docker compose up -d --wait. Verify a real browser conversion. The current upstream has no newer stable release since 2024.

Rollback / Откат

Return to the saved tag and tested configuration from backup. There is no server database; a new version may change browser storage independently.

Removal / Удаление

docker compose down removes the container and retains local config/env and browser data. Delete local files separately after backup; clearing the browser site deletes its preferences.

Verification

./smoke-test.sh uses Docker, Bash, curl, Python 3, Node >=22 and npm. It installs Playwright 1.62.1 and Chromium into a temporary test setup; Chromium system libraries must be available. It mutates only its own temporary recipe copy and removes it.

Report a recipe problem

Tell us how it went on your server

Opens a prefilled GitHub issue. A GitHub account is required; submitting the issue makes it public.

Troubleshooting

Troubleshooting

  • Cannot connect: check loopback port and the SSH tunnel. The container listens on 8080; the default published port is 8084.
  • Nginx fails: check config/nginx.conf, UID 101 readability and /tmp paths. Do not switch to root to mask a configuration error.
  • Missing favorites or input: state belongs to the browser; server backups do not contain it. Check origin, profile and private-browsing mode.
  • No Russian UI: the selected upstream release has no Russian translation. Russian documentation and samples do not alter the interface.
  • Environment setting has no effect: VITE settings apply at build time, not when the official static image starts.
  • Restore rejected: use your complete trusted archive and matching tag; invalid Nginx and incomplete archives are rejected before replacement.
docker compose ps
docker compose logs --tail=100 it-tools

Do not publish production browser input or secrets from your proxy configuration. Configure any required gateway protection separately before public access.

Official sources

Project website ↗Documentation ↗Source code ↗Issue tracker ↗

Latest release: 2024-10-22 · GitHub Stars: 40,962 · metadata checked Oct 25, 2026, 8:23 AM UTC

Disclaimer

Fossary is an independent informational catalog and is not affiliated with the developers of the listed applications. We collect information from public sources and verify published recipes, but we do not develop, distribute, or control these applications.

A listing or validation status is not a requirement, endorsement, or personal recommendation to use an application. You decide whether it is suitable and use it at your own risk. We do not warrant an application's security, availability, or fitness for purpose and, to the extent permitted by law, are not liable for resulting loss or damage. Review its license, security settings, data processing, and backup procedures before installation.