SShortSingh.

Programming

0
ProgrammingHacker News ·

Docket Tool Creates Per-Commit Evidence Records for AI-Generated Code

Docket is an open-source tool published on GitHub by developer Dillonsmart that generates evidence records tied to individual code commits. It is designed specifically to document and track code written by AI agents. The tool addresses growing concerns around accountability and auditability in software development as AI-assisted coding becomes more widespread. By attaching structured records to each commit, Docket aims to provide a verifiable trail of how and why code changes were made.

0
ProgrammingDEV Community ·

How to Verify Which Python Binary Your Code Actually Runs

Developers often assume commands like 'python' or 'pip' point to the correct interpreter, but this can silently cause errors in scripts and CI pipelines. On many systems, 'python' is either missing or aliased differently from 'python3', making explicit checks essential. Virtual environments add another layer of confusion, as a new shell session may not activate the venv even if the directory exists. Similarly, 'pip' and 'python3 -m pip' can belong to different interpreters, leading to packages being installed in the wrong environment. A short shell audit script using commands like 'command -v', 'sys.executable', and exit code checks can quickly confirm which binaries are actually in use.

0
ProgrammingDEV Community ·

GitHub Copilot Can Now Formally Approve Pull Requests, Counting Toward Branch Rules

GitHub updated its Copilot code review tool on 1 September 2026, allowing it to submit approvals that count toward a repository's required-approvals rule, the same way a human teammate's approval would. Previously, Copilot only left advisory comments and its reviews explicitly did not satisfy branch protection requirements. Administrators must actively enable the feature, and the approval is automatically dismissed if new commits are pushed, mirroring existing human-review behaviour. A follow-up update on 11 September added shell-tool execution during reviews, auto-resolution of Copilot's own comments, and an ensemble of agents that GitHub says improved detection of high-severity issues by 47%. The changes are currently in public preview and subject to change, raising governance questions about how AI approvals interact with enterprise and repository-level branch protection policies.

0
ProgrammingDEV Community ·

Opik: Open-Source LLM Observability Tool Lets Teams Self-Host Agent Tracing

Opik is an open-source, self-hostable observability platform for LLM agents, first created on May 10, 2023, and actively maintained with over 7,000 commits as of September 2026. The tool allows developers to trace every decision an agent makes before a failure occurs, addressing the common problem of discovering errors only after users complain. Licensed under Apache-2.0, Opik can be deployed entirely within a team's own infrastructure, with no data leaving the system and no enterprise sales process required. Beyond basic tracing, the platform bundles LLM-as-a-judge evaluation, prompt management, RAG assessment, guardrails, and CI/CD integration via PyTest into a single suite. Coding agents such as Claude Code, Cursor, and VS Code Copilot can also connect directly to Opik to read traces and run evaluations from within a chat interface.

0
ProgrammingDEV Community ·

Developer flags self-asserted test steps and untestable surfaces in E2E run

A developer running end-to-end tests on a sandbox project reported a 10/10 pass rate, but noted that one of the ten steps could not be externally verified — it was explicitly labelled as self-asserted rather than silently marked green. The untestable property concerned whether the binary correctly refuses unknown operation names, a check that is impossible to automate because the command interface has no argument slot through which a bad operation name can be passed. The developer argues this is a product observation, not a test limitation: if something cannot be tested from outside, it often also cannot be used from outside, and both gaps share the same fix. The remaining nine steps were validated across two independently created sandboxes, with all 46 output lines matching byte-for-byte, made possible by deriving environment identifiers from content rather than random allocation. An additional hour was lost to Git Bash silently rewriting POSIX paths before they reached the program, a transformation that produced no error and caused failures far from the actual source.

0
ProgrammingDEV Community ·

Developer Builds Immutable Invoice API Where Corrections Create New Documents

A developer published a TypeScript/Express REST API that enforces a strict invoice lifecycle, making finalized invoices immutable and handling corrections by issuing new replacement documents rather than editing originals. The system uses four states — draft, issued, canceled, and replaced — with replacement operations wrapped in a single database transaction to prevent inconsistent states. Despite achieving over 97% test coverage across 56 tests, two real bugs slipped through undetected by automated testing. One bug involved incorrect currency division that rendered Vietnamese Dong amounts as hundredths of their actual value on generated PDFs, a mistake the tests missed because both the code and expected test values shared the same flawed assumption. The incident highlights a key limitation of unit testing: automated tests confirm code behaves consistently with developer expectations, but cannot catch bugs rooted in incorrect assumptions themselves.

0
ProgrammingDEV Community ·

Developer Builds Local Tool to Filter SAM.gov Contractor Data Without API Limits

A developer has created the SAM.gov Public Contractor & NAICS Database Compiler, a tool designed to make the federal government's public bulk contractor dataset more accessible and searchable. The tool processes SAM.gov's official bulk extract locally, eliminating dependence on external API calls or third-party platforms. Users can filter contractor records by criteria such as NAICS codes, state, small-business status, CAGE code availability, and SBA classifications. Results can be exported to Excel or CSV, either as individual registration records or consolidated by unique entity. The tool is available as a standalone Windows executable and also supports a Python-based workflow for more technical users.

0
ProgrammingDEV Community ·

Misleading Error Code Hid a Missing Config Line, Not a Broken Parser

A build tool repeatedly reported a parse failure on a requirements document, leading developers to suspect either a malformed file or a broken parser — but both were intact. The real cause was a missing one-line declaration in the configuration, which meant the reader treated all 256 structured data rows as plain prose and found nothing to parse. The incident highlighted how error codes that name the stage of failure, rather than the underlying cause, can send investigators in the wrong direction. A second issue emerged during the fix: regenerating derived artifacts over a working tree with uncommitted edits produced inconsistent, non-reproducible results across consecutive runs. The author concluded that derived artifacts should only be generated and committed from a clean, committed state to ensure reproducibility.

0
ProgrammingDEV Community ·

Kairos Scheduler Offers Calendar-Aware Alternative to Cron for Complex Job Schedules

A developer tutorial published on DEV Community introduces Kairos, a scheduling tool designed to handle calendar-aware job scheduling that traditional cron cannot manage natively. Unlike cron, Kairos can account for time zones, public holidays, and business-day logic directly within schedule definitions, eliminating the need for wrapper scripts to handle edge cases. The article walks through five practical scheduling patterns — including business-day-only runs, true month-end detection, and payroll-style rolling dates — using 2026 US federal holidays as a reference dataset. Kairos does not replace a job runner such as systemd or a task queue; instead, it acts as a decision layer that determines whether a scheduled trigger should actually fire on a given day. The author recommends sticking with plain cron for simple fixed-interval tasks and adopting Kairos only when calendar complexity justifies the migration.

0
ProgrammingDEV Community ·

Kairos 1.0 launches as a schedule language built for composable business-day logic

A developer has released version 1.0 of Kairos, an open-source scheduling language designed to express complex date rules such as '3 business days before month-end' as composable expressions. Unlike existing tools such as cron or RRULE, Kairos allows calendar systems, holiday rules, and fiscal calendars to be user-defined rather than hard-coded. The reference implementation runs entirely client-side and derives observed holiday dates algorithmically, with no pre-built lookup tables. Evaluation is a pure function, making missed schedules enumerable and audit trails reproducible. The language has seen production use over the summer and is available via npm, with documentation and an English specification published at kairos-lang.org.

0
ProgrammingDEV Community ·

Developer Builds Reusable Python CLI Toolbox to Replace Repetitive AI-Generated Scripts

A Node.js developer built a Python command-line toolbox called Toolbox after growing tired of generating and discarding one-off AI-written scripts for routine tasks. The project, published on GitHub, handles file and image operations including CSV-to-Excel conversion, image grayscale, blur, compression, and PDF compression via rasterization. Built after completing a freeCodeCamp Python certification, it served as a practical way to apply new skills beyond just earning the certificate. The developer used the modern package manager uv to manage dependencies and virtual environments, finding its workflow closely mirrored familiar Node.js tooling. Standard library modules like argparse and csv were used alongside third-party packages Pillow and OpenPyXL to keep the toolbox lightweight and maintainable.

0
ProgrammingDEV Community ·

Developer builds open-source secrets manager to fix painful .env file sharing at work

A developer working in the financial industry created an open-source secrets manager called Dopbase after repeatedly struggling with his company's secure file-sharing process for .env files. Security policies at his workplace prohibited sharing environment files via email or messaging apps, requiring a multi-step approved channel that had to be repeated in full whenever any variable changed. The cumbersome workflow turned minor configuration updates into time-consuming administrative tasks, prompting him to build a dedicated solution. Dopbase is designed to keep secrets encrypted and access-controlled while eliminating the need for teams to manually pass updated files back and forth. The project is free, open source, and publicly available on GitHub for other developers facing similar challenges.

0
ProgrammingDEV Community ·

Developer Builds Crowdwide to Give Smaller Online Communities Equal Discovery Chances

Developer Puneet Kumar is building Crowdwide, a social and community platform designed to give smaller, lesser-known communities fairer visibility alongside larger ones. The platform aims to counter the common cycle on existing networks where already-popular communities continue to attract the most attention, leaving new or small groups largely invisible. Planned features include public and private communities, posts, articles, group chats, moderation tools, user profiles, and future monetization and algorithmic recommendation systems. Crowdwide recently won the KODA Online Fest Season 2 championship, though it remains in early alpha with account creation not yet open to the public. Kumar noted that a previous social platform project he built failed within a week, and said those lessons are informing his more security-conscious approach this time.

0
ProgrammingDEV Community ·

oxlint outpaces ESLint by 13x on Vue core, even with type-aware rules enabled

A developer benchmarked ESLint and oxlint against Vue's core repository — 445 TypeScript files totalling around 150,000 lines — using both syntactic and type-aware rule sets. ESLint completed the plain syntactic pass in 4.4 seconds and climbed to 12 seconds when type-aware rules were enabled, requiring the TypeScript compiler to run first. oxlint, a Rust-based linter built by VoidZero — the company founded by Vue and Vite creator Evan You — finished the syntactic pass in just 0.24 seconds, with its internal engine time recorded at 75 milliseconds. When oxlint's own type-aware mode was enabled via the --type-aware flag, it completed the same class of analysis in 0.9 seconds, roughly 13 times faster than ESLint's equivalent pass. The author noted that while the rule sets are not identical between the two tools, the results challenge the assumption that oxlint's speed comes from skipping expensive checks rather than from genuine performance gains.

0
ProgrammingDEV Community ·

How a deprecated cryptographic key exposed a flaw in schema validation design

A developer encountered a validation failure after adding a retired signing key whose scheme was no longer in the accepted set. Rather than widening the live set or discarding the old key, the solution was to introduce a separate 'schemes_retired' field, keeping the two sets distinct by capability rather than by time. The published specification was updated by retiring the old claim and adding a new scoped one alongside it, preserving an auditable record of the change. A pre-existing audit tool flagged the retired key as a violation, but this was logged as a known gap rather than silently patched, to avoid masking an underlying design flaw. The episode highlighted how naming conventions and set boundaries that appear cosmetic can carry real downstream consequences for counters, audits, and published guarantees.

0
ProgrammingDEV Community ·

Why a Single Accuracy Score Can't Measure Bot Detection's Real Cost

Bot detection systems that report high overall accuracy can still cause significant harm by wrongly blocking legitimate users, a problem known as false positives. The consequences vary sharply by route — a blocked checkout interrupts revenue, while a failed password reset locks out a real customer. Because most traffic on consumer-facing apps is legitimate, a detector can appear 99.7% accurate while still mishandling thousands of genuine requests daily. Experts recommend evaluating three separate metrics — precision, recall, and false-positive rate — rather than relying on a single aggregate score. Different enforcement actions such as hard blocks, challenges, and monitoring should each be governed by different thresholds based on the cost of each type of error.

0
ProgrammingDEV Community ·

AI Agent Authentication in 2026 Requires Layered Stack, Not a Single Protocol

As AI agents grow more complex, experts warn that no single protocol can handle their full authentication needs. A 2026 IETF Internet-Draft proposed a multi-layer architecture covering agent credentials, delegated user authority, workload identity, authorization, and audit trails. Google separately announced the open Agentic Resource Discovery (ARD) specification to help agents find and verify agentic capabilities without relying on hard-coded endpoints. Together, ARD, Web Bot Auth, OAuth, and workload identity standards each address distinct gaps in the agent identity chain. Collapsing these layers into a single API key, experts note, eliminates the audit trail and exposes systems to serious security risks.

0
ProgrammingDEV Community ·

How to Control Reasoning Effort in Codex CLI for Faster or Smarter Responses

OpenAI's Codex CLI offers a configurable 'model_reasoning_effort' setting that lets developers control how deeply the model reasons before responding, with five levels ranging from 'minimal' to 'xhigh'. The setting can be applied permanently via the ~/.codex/config.toml file, overridden for a single run using the -c flag, or adjusted mid-session with the /model command. Higher effort levels suit complex tasks like multi-file design changes or hard algorithms, while lower levels are better for simple fixes and formatting tasks. Developers can also bundle effort settings into named profiles for repeated workflows, such as code reviews requiring maximum reasoning. Additional keys like 'plan_mode_reasoning_effort' and 'agents.default_subagent_reasoning_effort' allow fine-grained control over planning mode and subagent behavior separately.

0
ProgrammingDEV Community ·

Browser Fingerprinting in 2026: JS Signals Fade as Network-Level Techniques Rise

Browser fingerprinting remains viable in 2026, but the landscape has shifted significantly as major browsers have neutralized many traditional tracking signals. Chrome, Firefox, Safari, and Brave have frozen or restricted JavaScript-accessible APIs such as User-Agent strings, navigator.plugins, and navigator.platform, rendering them largely useless for identification. Meanwhile, techniques like WebGL rendering, AudioContext, and TLS fingerprinting via JA4 continue to provide meaningful identifying signals due to hardware-level variation or network-layer operation. Network-level signals, including HTTP/2 settings and TCP/IP stack analysis, are increasingly favored because they operate below the browser API surface and cannot be blocked by privacy extensions. Experts caution that no single fingerprint should be treated as definitive proof of a visitor's identity or intent, and much of the guidance published just two years ago is now considered outdated.

← NewerPage 1388 of 3333Older →