Developer builds fully client-side toolkit so no code or data leaves the browser

·1 views

A South Korea-based web developer created a free online toolkit at juicydevs.com that runs entirely in the browser, ensuring no user data is sent to external servers. The project was motivated by privacy concerns around pasting sensitive code, database logs, or API payloads into third-party tools. The toolkit includes backend-focused utilities such as a SQL Log Binder for MyBatis and JPA logs, and an Excel-to-DDL converter for generating SQL or JPA entities. Frontend developers are also catered to with tools like a JSON-to-Zod schema generator and an SVG multi-format converter for Tailwind, CSS, and React Native. Standard formatters and decoders for JSON, SQL, and JWT are also included, with no sign-up or tracking required.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

How to Harden Your VPS With Firewall, SSH Config, and Fail2ban

Public servers face automated attacks within minutes of going online, including password brute-force attempts, port scans, and exploit probes. AhnLab's Q1 2025 report found that two malware families, P2PInfect and Tsunami, together made up around 80% of samples collected from compromised Linux SSH servers. A VPS typically sits behind two distinct firewalls: a provider-level network firewall managed via the hosting control panel, and a host-level firewall such as UFW or firewalld running inside the operating system itself. Security best practice recommends running both layers simultaneously, as each covers gaps the other cannot, rather than treating them as interchangeable. A default-deny firewall policy, hardened SSH settings, and Fail2ban together form a three-layer defence that can be configured in under an hour.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer builds workaround to trace slow queries inside Snowflake stored procedures

A developer found that Snowflake's ACCOUNT_USAGE.QUERY_HISTORY table lacks a PARENT_QUERY_ID column, making it impossible to directly link child statements to their parent stored procedure call. To work around this, they devised a SQL correlation technique using SESSION_ID and timestamp containment, selecting the tightest enclosing query window to reconstruct parent-child relationships. The approach was validated against edge cases including nested procedures, concurrent sessions, and rapid back-to-back calls, all of which produced clean, reliable results. Building on this, the developer created three diagnostic stored procedures to bulk-scan for regressions, drill into per-operator query profiles, and optionally request an AI-generated analysis via Snowflake Cortex. The tooling is designed to run under owner's rights, requiring only a one-time GRANT on ACCOUNT_USAGE to function across customer environments.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Why a CVSS threshold alone is not enough to filter vulnerability alerts reliably

A developer running a vulnerability write-up site built an automated triage script that pulls CVEs daily from two sources: NIST's NVD, filtered to CVSS scores of 7.0 and above, and CISA's KEV catalog, included in full regardless of score. The two sources were kept separate by design, as KEV confirms active exploitation while CVSS only predicts potential severity — merging them caused lower-scored but actively exploited bugs to be overlooked. A critical flaw emerged when failed data fetches and genuinely quiet days both returned zero results, making a broken pipeline indistinguishable from a clean one. The fix involved collecting errors explicitly and setting a non-zero exit code whenever a fetch failed, so callers could tell a truly empty result from a silent failure. The lesson is that a filtering threshold is incomplete until the system can distinguish between 'nothing found' and 'nothing was even checked.'

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Step-by-Step Guide to Building and Sharing Custom Docker Images

Custom Docker images allow development teams to standardize application environments by bundling specific OS versions, dependencies, and code into a single shareable unit. A practical approach involves first running all setup commands manually on a clean Linux system before translating them into a Dockerfile. The tutorial demonstrates building an image that runs a Flask web application on Ubuntu 24.04, including creating a Python virtual environment to comply with the OS's managed environment policy. A Dockerfile is then used to automate these steps, enabling the image to be built, run, and distributed consistently across any machine. Making the final image publicly available ensures all team members can pull and use the same environment, eliminating dependency conflicts.

0 comments Read more at DEV Community