Author: l0cknsec

  • Three GitHub AI Agent Automation Repositories Compared

    Three GitHub AI Agent Automation Repositories Compared

    The repositories receiving the most stars in the GitHub daily trending ranking on November 12, 2026, were the personal finance app we-promise/sure, addyosmani/agent-skills for AI coding agent skills, and the browser automation CLI vercel-labs/agent-browser. These repositories address different problems in self-hosting, development workflows, and AI agent automation.

    we-promise/sure: Self-host a personal finance app with Docker

    we-promise/sure is a community fork of the discontinued Maybe Finance project. The original project developed a personal finance and asset management app from 2021 to 2022, stopped development in mid-2023, and then released its source code. Sure maintains the codebase as an active, community-managed fork.

    • It provides personal finance and asset management features and supports full self-hosting through Docker.
    • It supports German, Spanish, French, Japanese, Korean, Portuguese, Russian, and other languages.
    • The community can participate through Discord, the website, and GitHub Issues.

    It is suitable for users who want to operate a personal finance app on their own server rather than subscribe to a separate hosted service. However, the source does not specify in detail how the community’s maintainers will develop the service in the future.

    It received 1,078 stars that day and had 13,264 stars in total as of November 12, 2026. Its primary language is Ruby. It is licensed under AGPL-3.0.

    addyosmani/agent-skills: Apply development standards to coding agents

    addyosmani/agent-skills provides production-grade engineering skills that help AI coding agents consistently follow experienced engineers’ workflows and quality standards. Slash commands connect the development lifecycle from specification and planning through implementation, testing, review, and deployment.

    • /spec defines what to build, while /plan breaks the work into small, atomic tasks.
    • /build implements one piece at a time, while /test validates the result through tests.
    • /constraints sets quality standards, while /review improves the code before it is merged.
    • /webperf measures web performance, /code-simplify simplifies the code, and /ship supports deployment.

    Once a specification is ready, /build auto can generate a plan and autonomously implement the approved tasks after a single approval. It is installed as a plugin command in Claude Code, and /review uses the /agent-skills:review format because its name overlaps with a built-in command.

    It received 787 stars that day and had 116,201 stars in total as of November 12, 2026. Its primary language is JavaScript. It is licensed under the MIT License.

    vercel-labs/agent-browser: Identify and manipulate elements from the shell

    vercel-labs/agent-browser is a browser automation CLI that lets AI agents open pages and manipulate elements through shell commands. The native CLI is written in Rust and keeps the browser open between commands, allowing each step to run through a short shell call.

    • snapshot converts a page into concise text based on its accessibility tree and assigns references such as @e1 to individual elements.
    • An agent can use those references to manipulate elements, read the page again, and repeat the process.
    • It can use CSS selectors, text, XPath, and role-based locators.
    • A click fails when the target is hidden, disabled, outside the viewport, or covered by another element.

    It is suitable for AI agents tasked with inspecting web pages and manipulating elements, as well as developers building command-line browser interfaces. On Linux, agent-browser install --with-deps also installs the browser’s system libraries, while npx agent-browser open example.com can be used without installation.

    It received 708 stars that day and had 50,081 stars in total as of November 12, 2026. Its primary language is Rust. It is licensed under Apache-2.0.

    Target users and comparison of the three repositories

    Repository Primary language Stars added today Total stars One-line purpose
    we-promise/sure Ruby 1,078 13,264 Self-host a Docker-based personal finance app
    addyosmani/agent-skills JavaScript 787 116,201 Standardize the development lifecycle for AI coding agents
    vercel-labs/agent-browser Rust 708 50,081 Automate browsers through shell commands

    Choose Sure to operate personal finance data directly, agent-skills to standardize coding agent development procedures, or agent-browser to automate web tasks. The daily and total star counts for all three repositories were recorded in the GitHub Trending daily ranking on November 12, 2026.

    Source

    This article was prepared by checking the following source: GitHub Trending, GitHub Trending 2026-11-12: sure, agent-skills, agent-browser

    Sources cross-checked:

  • DevOps Tool Priorities That Keep Work and Learning on Track

    DevOps Tool Priorities That Keep Work and Learning on Track

    When the demand to learn a new tool overlaps with work that must be finished today, it can be difficult to decide which one to handle first. Junior DevOps engineers in particular may have many unfamiliar procedures, which can keep expanding the scope of what they need to learn. However, the more time they spend trying to learn the names of every tool, the harder it becomes to set aside time for actual work.

    When work and learning compete for attention, it is better to select the minimum knowledge required for the current assignment and apply it immediately than to plan a large block of separate study time. Having limited experience and many tasks to complete is a natural part of onboarding. It does not mean that every piece of knowledge must be absorbed at once.

    Prioritization conflicts cause more problems than a lack of time

    A structural cause is that learning the tools used by the company is treated as a second task separate from the assigned work. This creates pressure to find study time after the work is finished, and even when time opens up, engineers must decide again which tools they need.

    The solution is to learn the tools required to complete the current assignment. Reading an overview of a tool is not the end of understanding. Engineers need to connect the commands, settings, logs, change procedures, and verification methods they use in the assignment with their actual work so that the knowledge stays with them.

    For assignments where operational stability is at risk, a verified procedure comes before incomplete learning. If a deadline is at immediate risk or a task could affect service operations, engineers should follow the existing team procedures and avoid applying newly learned features without approval. If a tool is used for repetitive, routine work, engineers can begin learning it through small changes.

    Select tools based on the current assignment

    Priority can be determined with a few questions. Can the assignment be completed without using this tool now? Is it difficult to reverse if a change goes wrong? Will the same knowledge be needed for future assignments? If the first two answers are yes, the tool should receive a higher learning priority. If the third answer is also yes, it can become a repeatable shared procedure. Tools that have not entered the work yet can remain on the list for later.

    In practice, checking the Git change status can help narrow the scope of the current work.

    git status
    git diff --stat
    git diff

    These commands provide a starting point for identifying which files have changed. Trying to review every modification at once, including changes unrelated to the current assignment, will expand the scope again. Reviewing only the files and changes directly connected to the assignment helps protect time for learning.

    Close short practice sessions with real verification

    When learning a tool, engineers should verify one minimum function in a safe environment. With Kubernetes, for example, they can begin with client-side verification before connecting to a production cluster.

    kubectl get pods --dry-run=client -o yaml

    This command only teaches how the client interprets a manifest and does not make changes to an actual cluster. Engineers should use a sandbox or personal practice environment approved by their team, and request credentials and change permissions only when necessary. Using the company’s practice environment like a personal experiment consumes the team’s operational capacity.

    After practicing, engineers should record where the commands they learned fit into the actual assignment. A useful record states which problem they solved, what they ran, and how the result differed from what they expected. This prevents them from tracing the same error from the beginning the next time it occurs. Records are better kept in the places the team actually uses, such as work tickets, pull request descriptions, or the team wiki, rather than only in personal notes.

    Common failures start with expanding the scope

    Starting every tool at once only increases the number of things to learn. A feature learned early may differ from the team standard and lead engineers to keep an individual approach. Before applying a new tool or setting, engineers should check the existing runbooks, pipeline configurations, and change history for infrastructure code. If differences appear, they should first follow the team owner’s guidance and verification procedure.

    The article started with a question posted on an r/devops post. Its main point is the need for clear selection criteria. Adjusting the intensity of learning according to the tools needed for the current assignment, the cost of recovery after a failure, and how often the work recurs can reduce conflicts between work and learning.

    Try these steps now

    • List the assigned tasks and their tools together, then mark the tasks that must be completed today.
    • Assess each tool in order of current need, risk of changes, and likelihood of repeat use, then choose one learning target.
    • Run one minimum function needed for the assignment with the selected tool in a safe environment and record the result.
    • Apply the learned command or setting to the actual assignment, then check whether it produces the same result as the existing team procedure.
    • Record what you learned today, any remaining questions, and the point for the next iteration in a work ticket or the team wiki.

    Source

    This article was written after reviewing the following source: r/devops, How to learn while also completing tasks?

  • Gemini Decisions API evaluates tool choices and policies

    Gemini Decisions API evaluates tool choices and policies

    Google unveiled the Gemini Decisions API on November 11, 2026. The new endpoint, available through the Gemini API and Google AI Studio, is based on the Gemini Decision 1 model and evaluates AI decisions such as tool selection and policy checks using the probabilities and confidence levels of a limited set of candidates.

    Multimodal inputs and questions processed together

    Text, images, audio, video, and PDFs can be combined into a single shared input. The input limit is 256K tokens, and the same input can support up to 1,000 independent questions. Adjusting the resolution of images or video lets developers control visual detail and token costs. The API can also assess call recordings together with account details, or scanned invoices together with photos of damage.

    Input fields use the Content block format from the Interactions API. Gemini Decision 1 does not generate answer sentences token by token. It calculates the scores of candidate choices in a single forward pass and returns the selected result with its probability. This approach is designed for tasks that require decisions within a defined set of candidates, including tool selection, model routing, and context evaluation.

    Conditional judgments and ranking with noul, choice, and score

    Questions are divided into three types. A noul question estimates the probability that true and false conditions will apply. A choice question selects one of 2 to 255 candidates and returns a normalized probability for each candidate. A score question calculates a continuous weighted score and grade-level probabilities according to an ordinal rubric that starts at 0. A single request can combine different question types to evaluate the same input.

    Every result includes a confidence score between 0 and 1. Applications can use this value to automate clear cases and route ambiguous cases to a fallback path or human reviewer. Probabilities indicate the likelihood of each choice and condition, while the confidence score helps applications set their own thresholds for trusting the result.

    Low latency, low cost, and probability calibration

    Google reported a median model computation latency of 50 to 100 milliseconds and an end-to-end latency of 150 to 250 milliseconds for Gemini Decision 1. Latency remained nearly constant as the number of questions increased from 1 to 100, and multimodal inputs and contexts were evaluated with up to 16K tokens. The benchmarks covered agent routing, reasoning, ranking, and multimodal understanding. Google said the model achieved the best performance and the lowest calibration error in its internal evaluation. These figures require independent verification.

    The price is $0.10 per 1 million input tokens, with no charge for output tokens. A shared input is charged once per request regardless of the number of questions, with additional charges only for the instructions and criteria tokens of each question. Output tokens, thinking tokens, and separate audio transcription and OCR charges are not billed. Google said the API was nearly five times cheaper than a combination of Gemini 3.5 Flash-Lite and the Interactions API on a shared benchmark.

    Model routing and safety checks in Google products

    Gemini Notebook uses the Decisions API as a real-time model router, sending requests to the appropriate model tier and reasoning level. Google said it handled routine requests quickly while reserving deeper reasoning models for complex requests, reducing latency by up to 40%.

    Stitch uses the Decisions API in its rapid canvas experiment to generate playable wireframes of product flows and apply edits specified by voice or tabs. CC selects reactions from a palette of more than 200 emojis, while Google Search detects adversarial behavior in its MCP tool safety layer. API keys can be issued through Google AI Studio, which also provides Python, JavaScript, and REST guides along with the Doorstep Parcels, Speed Sketch, and Find the Zoo Keeper demo applications. Ecosystem integrations with OpenRouter, LangChain, Vercel, LiteLLM, Pydantic AI, Pipecat, LiveKit, and other platforms are also underway.

    According to Google’s Gemini Decisions API announcement, developers can obtain an API key and begin prototyping in Google AI Studio.

    Source article

    This article was written after reviewing the following source: Google Research Blog — Gemini Decisions API: Fast, calibrated multimodal decisions

  • Samsung, SK Hynix Shift More eSSD Supply to US Customers

    Samsung, SK Hynix Shift More eSSD Supply to US Customers

    On November 12, 2026, Samsung Electronics, SK Hynix and other memory manufacturers were reportedly preparing to allocate additional enterprise SSD (eSSD) volume that they had been discussing with Chinese customers to US buyers. The impact of China’s reduced eSSD orders may emerge as a higher share of supply for the US market rather than spread across the entire storage memory market.

    Why Chinese AI companies are reducing eSSD orders

    Major Chinese AI companies including Alibaba, Baidu and Tencent have decided to reduce their eSSD order volumes by more than expected, and memory manufacturers are aware of the change.

    The reduction is attributed to tighter US export controls on high-performance AI semiconductors and high-bandwidth memory (HBM). The US government has effectively prohibited exports of advanced AI semiconductors from major companies such as Nvidia and AMD to China, and HBM used with AI chips is also subject to restrictions.

    Chinese companies have tried to bypass the controls through overseas subsidiaries or by disassembling products, but those workarounds have been blocked, disrupting some investment plans. Their storage requirements have also fallen as the amount of memory installed alongside AI chips has decreased, leading them to adjust planned eSSD purchases.

    How Samsung Electronics and SK Hynix are changing US supply

    Samsung Electronics and SK Hynix have adjusted their supply plans to allocate some eSSD volume that had been designated for Chinese customers to US buyers. The reduced China-bound volume is expected to be absorbed by US data center companies.

    Shortages of high-capacity, high-efficiency eSSD have continued as data processing volume increases at data centers that process images and train AI models. An eSSD is a NAND-based memory module installed mainly in data centers and serves as secondary storage for data. Product lines suited to high-capacity storage, such as Samsung Electronics’ ninth-generation QLC V-NAND technology, are being used to address the shortage.

    Industry sources said the supply plan for China has been adjusted, although the volume is already shifting to US cloud service providers (CSPs). The specific volume and percentage of reductions by Chinese customers, as well as the exact additional volume and customer names assigned by the two memory manufacturers, have not been disclosed.

    Why this is unlikely to signal a broader decline in SSD demand

    Reports suggest that the reduction in eSSD orders will not have a major effect on overall NAND and SSD demand. NAND supply shortages continue in global markets including the US, allowing US data centers to absorb some of the decline in Chinese demand.

    Memory demand for US data centers remains firm, and shortages are likely to continue through next year and the year after. The adjustment is therefore closer to memory companies reassigning regional demand and supply volumes affected by export controls than a decline in total storage memory demand.

    Further details are available in ZDKorea’s original article.

    Source article

    This article was prepared after reviewing the following source: China, AI chip shortage drives eSSD ‘order cuts’… Samsung and SK increase US supply

    Sources cross-checked:

  • Apache HTTP/2 flaw risks remote code execution

    Apache HTTP/2 flaw risks remote code execution

    A remote code execution vulnerability, CVE-2026-119618, has been discovered in mod_http2, the HTTP/2 module for Apache HTTP Server. Apache HTTP Server versions 2.4.55 through 2.4.70 are affected. Apache released the fixed version 2.4.71 on November 11, 2026.

    Affected versions and HTTP/2 exposure conditions

    This Apache HTTP/2 vulnerability affects only servers with HTTP/2 enabled. An attacker who can access the server may be able to exploit the vulnerability without authentication and could potentially take control of the entire server process. Red Hat rated the vulnerability CVSS 9.8.

    HTTP/2 is enabled through Apache’s Protocols directive. HTTP/2 over TLS is specified as h2, while HTTP/2 over plain TCP is specified as h2c. The configuration can apply to the entire server or to individual virtual hosts. Administrators should check the configuration for every virtual host, not only the global configuration.

    The scope of the vulnerability differs between the official Apache project distribution and the standalone mod_h2 release distributed through GitHub.

    Configuration Affected versions Fixed version or status
    Apache HTTP Server 2.4.55 to 2.4.70 2.4.71
    standalone mod_h2 2.0.8 to 2.0.42 No fixed release available
    Red Hat Enterprise Linux 9 Separate package mod_http2-2.0.26-7.el9_9.1
    Red Hat Enterprise Linux 10 Separate package mod_http2-2.0.29-5.el10_3.1
    Red Hat Enterprise Linux 6 to 8 Vulnerable code not included No separate action required

    Apache patches and updates by distribution

    Organizations operating the Apache HTTP Server project distribution were advised to update to version 2.4.71. This fixed version also addresses an important crash in mod_md and a one-byte stack memory overwrite in mod_vhost_alias.

    Red Hat Enterprise Linux uses its own builds and package versioning, so it can be difficult to determine whether an update has been applied based on Apache’s version number alone. The fix for RHEL 9 is available as mod_http2-2.0.26-7.el9_9.1, while the fix for RHEL 10 is available as mod_http2-2.0.29-5.el10_3.1. Fixes are also available for RHEL 9.4 Update Services for SAP Solutions, RHEL 9.6, 9.8, 10.0, and 10.2 Extended Update Support.

    Red Hat classified the issue as Important rather than Critical on RHEL 9 and 10. The company said it rated the vulnerability lower because the affected package uses a separate memory allocator for each HTTP/2 stream, making exploitation more difficult. The vulnerability is listed in the security trackers for Debian bookworm, trixie, and forky, as well as Amazon Linux 2 (Core), 2023, and 2027 Preview. As of the day The Hacker News checked, there was no corresponding vulnerability page in Ubuntu’s CVE tracker.

    Disabling HTTP/2 and the status of public exploits

    Apache’s official advisory did not provide a workaround. Until the update is applied, administrators can reduce exposure by removing h2 and h2c from the Protocols settings for the server and every virtual host, leaving only Protocols http/1.1. Wiz recommended disabling HTTP/2 in this way, and the same change applies to servers using the standalone mod_h2 package.

    Reports about publicly available exploit information have differed. Red Hat said trusted public exploit research exists for servers with mod_http2 enabled in the default configuration, but did not publish the research name or link. Wiz said no exploit had been published that day and that it had found no reports of attacks in real-world environments. The absence of public information and the absence of attacks should therefore not be treated as equivalent.

    Anthropic’s OSS Scanner discovered the vulnerability on October 26, 2026. Anthony Weems and Simon Scannell reported it the following week through Google Cloud Vulnerability Research.

    Status of servers with only previous HTTP/2 patches

    The previously disclosed HTTP/2 vulnerability, CVE-2026-23918, was fixed in Apache HTTP Server 2.4.67 on May 4, 2026. However, servers updated to that version or to a later version up to 2.4.70 remain affected by CVE-2026-119618.

    Source

    This article was prepared by checking the following source: The Hacker News, Critical Apache HTTP/2 Flaw Could Let Unauthenticated Attackers Execute Code Remotely

    Cross-referenced sources:

  • EU Digital Fairness Act targets loot boxes and AI chatbots

    EU Digital Fairness Act targets loot boxes and AI chatbots

    The EU Digital Fairness Act (DFA), proposed by the European Commission, would regulate features that encourage excessive use of consumers’ time and money on gaming, social media and e-commerce platforms. Its rules would cover loot boxes and influencer advertising, as well as AI chatbots, dynamic pricing, payments by minors and subscription cancellation. It remains a pre-legislative proposal, and the final provisions for each area subject to regulation have not been settled.

    Platforms and features covered by the EU Digital Fairness Act

    The DFA would prohibit manipulative marketing and dark patterns that manipulate purchasing decisions. Dark patterns refer to methods of designing interfaces and purchasing processes to encourage purchases that consumers would not otherwise have made. False inventory messages that make products appear nearly sold out are a common example.

    Rules for addictive design features would give users the option to disable them. These features include persistent notifications, infinite scroll and automatic video playback. The proposal says the same restrictions would apply to AI companions and general-purpose conversational chatbots. This could expand the scope of product design reviews covering recommendation algorithms and methods used by chatbots to encourage users to return.

    Loot boxes and protections for minors and influencers

    For gaming, provisions governing gambling-like features that encourage excessive spending are a central issue. Features such as pay-to-win and pay-to-progress would be prohibited for minors. Pay-to-win refers to systems in which players can pay for an advantage, while pay-to-progress refers to systems that require payment to continue. Virtual currency purchases and microtransactions would also be regulated.

    Influencers would have to clearly identify sponsored content, and advertisements that rely on children’s trust would be restricted. Personalized advertising and pricing decisions would also face restrictions on practices that target minors or exploit sensitive data. Some gaming organizations have argued that proposed regulation of virtual currency, loot boxes and microtransactions involving minors would be impossible to enforce, unfair and excessive.

    Subscription cancellation, price disclosure and the right to speak with an AI service

    The proposal includes provisions intended to make it easier to cancel subscriptions and digital contracts. They also cover notifications about upcoming automatic renewals and the end of free trials. Prices would have to be displayed clearly and transparently during dynamic pricing and in-app virtual currency purchases. For ticket waitlists for cultural and sporting events, the current price would have to be shown in real time, up to the highest available price.

    Consumers would have the right to communicate with a human customer service representative. The proposal says this right would also be guaranteed when an AI agent processes a purchase. The provisions address procedures for securing access to a human representative for services that otherwise provide only automated support. Further details of the proposal are available in The Verge’s report on the Digital Fairness Act.

    Legislative process and unresolved issues

    The DFA is currently at the proposal stage and must receive approval from the European Parliament and the Council of the European Union. Current provisions could be amended or removed entirely during the legislative process. The final implementation date and detailed requirements therefore remain unsettled.

    Penalties for violations could reach up to 6% of a company’s worldwide annual revenue after the proposal takes effect, but the actual enforcement date and method would depend on the outcome of the legislative process. Reviews by product providers would cover pricing and payment screens, settings for ending recommendation features, advertising disclosures, procedures for transferring customers to human support and restrictions on payments by minors. These areas would be reviewed separately from their current status because the enforceability of the EU Digital Fairness Act could be reflected directly in the cost of design changes.

    European Commission Vice-President Michael McGrath said, “Our consumer protection rules will help ensure that businesses compete on the merits of their products and services, not on their ability to exploit consumers or evade the rules. We are not making it harder to do business. We are making it harder to do business unfairly”.

    Source

    This article was prepared by consulting the following source: The Verge: Loot boxes, influencers, and addictive features face an EU crackdown

  • GitHub Trending 2026-11-09: Top 3 Repositories

    GitHub Trending 2026-11-09: Top 3 Repositories

    The top three repositories with the largest increases in stars in the GitHub Trending daily ranking collected on 2026-11-09 were sherlock-project/sherlock, milind-soni/OpenMausBot, and meta/astryx. sherlock finds social media accounts by username, OpenMausBot provides a team of AI agents that runs locally, and astryx provides a design system that people and AI can use together.

    sherlock: A social media account search tool

    sherlock-project/sherlock is an information gathering project that takes a specific username and finds accounts across multiple social networks. Search results are saved in separate text files corresponding to each username, and the command-line interface supports searches for one or multiple users.

    • Searches for username-based accounts across more than 400 social networks.
    • The primary language is Python, and the project is distributed under the MIT license.
    • Covers topics including CTI, cybersecurity, forensics, and information gathering.

    sherlock is suited to security, forensic, and information gathering tasks that require locating all public accounts associated with a specific user across multiple sites. However, the README warns that third-party packages for ParrotOS and Ubuntu 24.04 may not work. Users of those operating systems are advised to use uv, pipx, pip, or Docker instead.

    OpenMausBot: A local-first AI agent team

    milind-soni/OpenMausBot is an open-source application that can replace Grok Bot. It provides a team of AI bots focused on its own models and local execution. Each agent in the conversational app runs Claude or Codex locally, with its own personality and model, cloud computer, and connected applications.

    • Users can chat with agents like contacts and check their progress.
    • Supports workflows in which users approve important tasks.
    • Lists AI agents, Claude Code, Codex, computer use, Docker, and Electron as repository topics.

    OpenMausBot suits teams that organize multiple models as separate workers and assign tasks through connected applications. Signed and notarized dmg files for Apple silicon and Intel are available for macOS, along with an x64 installer for Windows and x64 deb or AppImage beta releases for Ubuntu 24.04. Its configuration approach for AI agent connection tools overlaps with the analysis of three AI agent connection tools.

    astryx: A design system for people and AI

    meta/astryx is an open-source design system intended for a development model in which people and agents work side by side. It is currently in beta. It is based on React 19+ and StyleX, allowing consumers to use prebuilt CSS and typed React components without adding separate build plugins or style libraries.

    • Provides more than 150 components designed with accessibility in mind.
    • Includes brand-level theming, dark mode, ready-to-use templates, and a CLI.
    • The swizzle function allows users to extract a component’s full source code into a project and take direct ownership.

    astryx is suited to engineering, design, and product teams that manage shared interfaces and brand styling across multiple applications. The repository says it grew inside Meta for eight years and supports more than 13,000 applications, but this figure is a claim made by the project itself.

    Repository Primary language Stars added today Total stars One-line purpose
    sherlock-project/sherlock Python 2,373 104,366 Searches for username-based accounts across more than 400 social networks
    milind-soni/OpenMausBot TypeScript 1,439 18,591 Provides a local-running team of personal AI agents and approval-based task workflows
    meta/astryx TypeScript 875 17,328 Provides an accessibility-focused design system that people and AI can use together

    sherlock addresses environments where the goal is to locate a specific user’s presence across social networks, while OpenMausBot fits AI agent environments involving local models and connected applications. astryx is intended for development environments that manage shared UI components and brand theming across an organization. These three repositories in this GitHub Trending ranking supported different areas of work: account searches, agent team operations, and design systems.

    Source references

    This article was written after reviewing the following source: GitHub Trending — GitHub Trending 2026-11-09: sherlock, OpenMausBot, astryx

    Cross-checked sources:

  • How to manage.env files in private repositories

    How to manage.env files in private repositories

    When you operate multiple repositories, one of the most tedious tasks is manually copying the same configuration files. Every time you rebuild a server or add a team member, you paste values into place and lose track of which repository has the latest version. A private repository can provide change history and pull request reviews, so doing environment variable separation correctly can make configuration management easier.

    Judge.env values individually instead of banning every.env commit

    The original project is divided into a Docker repository, a backend repository, and an indexer repository, with each repository containing its own.env file. These files include secrets such as database passwords, API keys, and tokens, as well as non-secret values such as private IP addresses for fixed servers and backend tuning parameters that change with VPS resources and workload.

    Keeping passwords out of Git and keeping non-secret configuration files out of private repositories are two different decisions. Secrets should be injected from outside the repository, while only non-secret configuration should be managed with Git. A.env file is a format for delivering configuration, not a security boundary. The risk depends on the values it contains and who can access them, not on its filename.

    A private repository is not a fully isolated space. Broad repository permissions or weak account management can expose internal addresses and the operating structure. Private IP addresses are not credentials themselves, but they can reveal internal topology, so teams and individuals whose access may be exposed to the public must be identified first. Tuning parameters should also be classified after confirming that combining them with another authentication method does not expand access.

    Separate values into three categories

    Secrets include values that can lead to account takeover or data access if exposed, such as database passwords, API keys, and tokens. Do not store them in Git. Inject them as environment variables or files during deployment. Sensitive configuration includes values such as private IP addresses that reveal internal structure but do not grant access on their own, so limit access to authorized members. General configuration includes tuning parameters that are close to public information and would cause limited harm if exposed, so these can use Git history and pull request reviews.

    For each value, record answers to three questions: who can read it, what harm would exposure cause, and which runtime component reads it. If any answer is unclear, do not classify the value as general configuration until the owning team and access scope have been agreed upon. Addresses and account information that become more sensitive when combined with secret values should receive the same treatment as secrets.

    Split configuration across repositories into shared values and differences

    When shared configuration is copied into each repository, a change may update only some files and leave values inconsistent. Collect shared configuration in a separate configuration repository or deployment artifact, and keep a.env.example file in each repository that lists only the required keys. Separate environment-specific differences with override files.

    For example, a shared repository can version general configuration and environment-specific overrides. The Docker repository can own the compose files needed for deployment, the backend repository can own the application configuration template, and the indexer repository can own the collector configuration template. Actual secret values should not be placed in the shared repository either, and should instead be injected in each deployment environment.

    git grep -nE '(PASSWORD|SECRET|TOKEN|API_KEY)' -- ':!*.example'
    git ls-files --.env
    git log --all --oneline --.env

    These commands provide a basic workflow for checking for secret keys that may remain in a repository, whether.env files are tracked, and what changes were made in the past. Finding a value does not mean it has been removed automatically, so review both the current files and the historical record. Git retains committed content in its history, so a commit that deletes a secret does not erase the exposure history. If exposure is suspected, rotate the affected credentials and review access logs before proceeding with the history cleanup process.

    End secret injection at the deployment boundary

    Environment variable separation should do more than create a separate secret store. It should minimize access and deliver values only to the services that need them during deployment. Even if encrypted values are stored in Git, the decryption key must remain outside the repository. This approach also loses its protection if key management fails, so record the key storage location, authorized readers, rotation schedule, and responsible team in the operating procedure.

    Moving every value into a secret injection system, on the other hand, complicates deployment pipelines and access management whenever the configuration changes. First create a classification table, review general configuration through pull requests, and inject only secrets through a separate path. This reduces the maintenance burden. The original configuration can be reviewed in the discussion about committing configuration-only.env files.

    In practice, start by dividing the current.env values into secrets, sensitive configuration, and general configuration, and record the potential harm of exposure and the component that references each value. Then use git grep and Git history to check whether secrets have been exposed, and organize the configuration structure with.env.example files and environment-specific overrides. Limit private repository permissions to the members who need access and include the change procedure in pull request reviews. If secrets are found in the history, rotate the credentials and review access logs before deleting the values.

  • MoE Routing Compared: DeepSeek, Kimi, Llama 4

    MoE Routing Compared: DeepSeek, Kimi, Llama 4

    Ten open-source mixture-of-experts models select different experts for each token, but their routing structures differ substantially. Public configurations list 8 to 384 experts and top-k values from 1 to 8, with some models using shared experts that always run and others without them. These differences in MoE routing affect GPU deployment and can be examined in a comparison published on November 8, 2026.

    How many experts does each model select for each token?

    All models in the comparison use token-choice routing, which selects experts at the token level. Their configurations differ in five areas: total expert count, number selected per token, shared experts, scoring function, and load-balancing method.

    Model Routing experts top-k Shared experts Gating and balancing method
    Mixtral 8 2 0 Softmax, selection-score normalization
    DeepSeek-V3 256 8 1 Sigmoid, bias-based balancing without the noaux_tc auxiliary loss
    DeepSeek-V4-Pro 384 6 1 sqrtsoftplus, noaux_tc, hash routing in the first three MoE layers
    Qwen3 MoE 128 8 0 Global-batch auxiliary loss
    Qwen3.6-35B-A3B 256 8 1 Gating details not disclosed
    Llama 4 Maverick 128 1 1 Gating and balancing method not disclosed
    gpt-oss-120b 128 4 0 Linear router, balancing method not disclosed
    Kimi K2 384 8 1 noaux_tc and sequence auxiliary loss
    GLM-4.5 160 8 1 Loss-free balance routing

    How DeepSeek and Kimi K2 changed their routing

    DeepSeek-V3 evaluates 256 routing experts with sigmoid and normalizes the selected scores. Per-expert biases guide top-8 selection without changing the mixing weights, and tokens are sent to at most four of the eight groups. Every token also passes through one shared expert.

    DeepSeek-V4-Pro increased the number of routing experts from 256 to 384 while lowering top-k from 8 to 6. Its scoring function changed to sqrtsoftplus, but it retained bias-based noaux_tc balancing. The first three MoE layers use hash routing, a fixed token-to-expert mapping.

    Kimi K2 uses the DeepseekV3ForCausalLM architecture class and a noaux_tc router. It increased the number of routing experts to 384 while keeping top-8 selection. Its technical report says that increasing sparsity at a fixed activation compute budget reduced loss. GLM-4.5 chose to increase its number of layers instead of selecting 160 experts.

    How Llama 4 and gpt-oss process tokens

    Llama 4 Maverick alternates dense and MoE layers. In each MoE layer, a token activates one shared expert and one of 128 routing experts. The model has 400B total parameters, with 17B active parameters.

    gpt-oss-120b applies a linear router to 128 experts, selects the top four, and has no shared experts. The 117B model with MXFP4 weight format was reported to fit on a single 80 GB GPU. In contrast, Llama 4 and gpt-oss do not disclose their balancing methods in their configuration files. The configurations and model cards for Llama 4 and Qwen3.6 do not specify their gating details.

    What determines GPU deployment and all-to-all communication

    More experts mean more resident weights in each layer and greater all-to-all communication requirements for expert parallelism across GPUs. A lower top-k reduces computation and data transmission per token, while shared experts create a dense path that every token passes through.

    Active parameter counts alone are insufficient for cost comparisons. Qwen3.6-35B-A3B lists 35B total parameters and 3B active parameters, while DeepSeek-V4-Pro lists 1.6T total parameters and 49B active parameters. DeepSeek-V4-Pro and Kimi K2 require multi-GPU expert parallelism.

    GPU count calculations must account for total weights, expert placement, top-k, shared-expert paths, and communication methods in addition to active parameters. The source recommends checking these factors before determining GPU size. Finally, Kimi K2’s comparison report says that sparsity 48 used 1.69 times fewer FLOPs than sparsity 8 at the same validation loss.

    Source

    This article was prepared by consulting the following source: MarkTechPost: Which Routing Does Each MoE Model Use? DeepSeek, Qwen, Mixtral, Llama 4, gpt-oss Compared

  • AI complaints surge, straining UK public bodies

    AI complaints surge, straining UK public bodies

    Businesses, local authorities, courts, schools and public bodies across the UK are facing heavier workloads as AI-generated complaints, letters and legal challenges increase. Holly Wickins, who works in the office of a Labour MP, said half of the emails she receives appear to have been written by AI. This trend is being called an “AI complaint surge,” with the gap between document generation and processing times adding to workload pressures on public bodies.

    AI complaints increase workloads

    Until the year before last, writing a complaint or applying for a local planning review required research, completing forms and specialist knowledge. As generative AI tools such as ChatGPT, Claude, Copilot and Gemini became widely accessible, members of the public began using free legal advice and action tools as everyday resources. These documents can be produced in seconds, but staff spend much longer reading them, checking the facts and requests, and preparing replies.

    The Information Commissioner’s Office said that several public bodies received more freedom of information requests in 2025. It explained that AI-written requests tend to be long and repetitive, often including irrelevant opinions and demands directed at the wrong issue, making the actual request difficult to identify. Before AI became widely used, complaints received by local authorities averaged about two pages, but most are now ten times longer, according to Deborah Evans. The longest document currently known runs to about 200 pages.

    Complaint types concentrating public attention

    Complaints received by local authorities cover issues including adult social care, missed refuse collections, parking violations, planning application appeals and parking ticket appeals. Alessandro Georgiou, a councillor on Enfield Council, said parking appeals had increased sharply as more residents challenged council decisions. Deborah Evans, who represents Lawyers in Local Government, said similar problems were appearing across every industry.

    Researchers from the Hertie School’s Center for Digital Governance in Berlin, the Cooperative AI Foundation and GovAI called the practice of overwhelming public bodies with AI-generated requests “agentic flooding”. The sharp increase in complaints consumes existing staff time and resources in local authorities, which have not received additional funding.

    Accuracy risks in AI legal documents

    AI can treat complaints as legal arguments and cite statutes and court cases, but it may apply precedents outside an authority’s jurisdiction or invent facts. Cases from other jurisdictions, such as Canada, may also be cited as grounds. Some business owners said they were concerned that AI could be overly supportive of users, give them false confidence in their position and encourage them to take legal action without proper verification. One technology startup founder said a former employee submitted what appeared to be an AI-generated document in an employment tribunal dispute over their dismissal.

    According to UK government figures, single cases initiated at employment tribunals from April to June increased 28% year on year, reaching 14,000. The number of cases concluded during the same period fell, leaving 70,000 single cases outstanding at the end of June. With a substantial backlog already in place, the founder was expected to spend about £30,000 on tribunal hearings and legal fees. However, publicly available information cannot confirm whether AI designed the legal strategy in every case.

    Responsibility when handling AI requests

    The Information Commissioner’s Office cautioned that requests appearing to be written by AI may still contain errors, but that people remain responsible for handling and answering them directly. However, the source did not set out specific criteria for determining whether all AI requests could be classified in the same way or which requests could be processed automatically.

    The Information Commissioner’s Office cautioned that requests appearing to be written by AI may still contain errors, but that people remain responsible for handling and answering them directly. However, the source did not set out specific criteria for determining whether all AI requests could be classified in the same way or which requests could be processed automatically. The AI complaint surge is adding to the burden of ensuring legal accuracy and answering responsibility.

    The impact on UK public bodies from AI-generated complaints and legal response letters is examined in The Guardian’s report on AI clog.

    Source article

    This article was prepared by reviewing the following source: The Guardian Tech, “AI clog”: UK public bodies battle onslaught of chatbot-generated complaints