# Repository

A repository is a store of data or computer files that can be accessed and managed through defined methods.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## f2x50: A Repository-Scale Benchmark for Fortran-to-X Software Migration

DevFeed: [f2x50: A Repository-Scale Benchmark for Fortran-to-X Software Migration](<https://devfeed.tech/articles/f2x50-a-repository-scale-benchmark-for-fortran-to-x-software-migration-142143.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.23268>)

Author: Shraddha Surana, Ashwin Srinivasan

Published: 2026-11-19T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [Fortran](<https://devfeed.tech/topics/fortran.md>), [Benchmark](<https://devfeed.tech/topics/benchmark.md>), [Compilers and Linkers](<https://devfeed.tech/topics/compilers-and-linkers.md>), [Repository](<https://devfeed.tech/topics/repository.md>)

Tags: [benchmark](<https://devfeed.tech/tags/benchmark.md>), [cs-pl](<https://devfeed.tech/tags/cs-pl.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [fortran](<https://devfeed.tech/tags/fortran.md>), [migration](<https://devfeed.tech/tags/migration.md>), [python](<https://devfeed.tech/tags/python.md>), [repository](<https://devfeed.tech/tags/repository.md>), [reproducibility](<https://devfeed.tech/tags/reproducibility.md>), [scale](<https://devfeed.tech/tags/scale.md>), [software](<https://devfeed.tech/tags/software.md>), [software-migration](<https://devfeed.tech/tags/software-migration.md>), [translation](<https://devfeed.tech/tags/translation.md>)

### AI overview

f2x50 benchmarks repository-scale Fortran migration across 50 public repositories pinned to exact Git revisions, addressing behavior across modules, shared state, build structure, and dependencies. It includes 12,116 tracked Fortran files, 6,569,806 lines, three structural-complexity tiers, and 561 deterministic behavioral probes. Of these, 446 compile pinned source files with small drivers and cover 131 repository-routine pairs; each repository has at least five direct checks collectively executing at least two routines. Other probes are labeled as extractions, inline reimplementations, or synthetic fixtures. The benchmark supplies target-independent acquisition, validation, license-review, and reproducibility tools, plus a reference adapter for Python targets, to support comparable evaluations across migration tools and target languages.

### Source excerpt

arXiv:2611.23268v1 Announce Type: new Abstract: Repository-level migration requires more than translating isolated functions: it must preserve behaviour across modules, shared state, build structure, and dependencies. Existing translation benchmarks predominantly cover small programs or small repositories, or fixed and widely studied language pairs. We present f2x50, a target-independent benchmark comprising 50 public Fortran repositories pinned to exact Git revisions. It contains 12,116 Git-tracked Fortran files and 6,569,806 lines, divided into three structural-complexity tiers and paired with 561 deterministic behavioural probes. Of these probes, 446 compile pinned source files with small drivers and span 131 repository--routine pairs. Every repository has at least five direct checks that collectively execute at least two routines. f2x50 provides target-independent tools for acquisition, validation, licence review, and reproducibility, together with a reference adapter for evaluating Python targets. The remaining probes are explicitly classified as extractions, inline reimplementations, or synthetic fixtures. The benchmark therefore supports comparable evaluations across migration tools and target languages.

## JET: Just-Enough Exploration Tuning for Efficient Tool-Calling Agents in Repository-Level Question Answering

DevFeed: [JET: Just-Enough Exploration Tuning for Efficient Tool-Calling Agents in Repository-Level Question Answering](<https://devfeed.tech/articles/jet-just-enough-exploration-tuning-for-efficient-tool-calling-agents-in-repository-level-question-answering-140046.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.22539>)

Author: Yoonho Choi, Taehyeon Han, Seonghyeon Lee

Published: 2026-11-18T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Artificial Intelligence](<https://devfeed.tech/sources/arxiv-artificial-intelligence.md>)

Topics: [Fine-tuning](<https://devfeed.tech/topics/fine-tuning.md>), [Multi-step AI processes](<https://devfeed.tech/topics/multi-step-ai-processes.md>), [Tool](<https://devfeed.tech/topics/tool.md>), [Repository](<https://devfeed.tech/topics/repository.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [benchmarks](<https://devfeed.tech/tags/benchmarks.md>), [code](<https://devfeed.tech/tags/code.md>), [cost](<https://devfeed.tech/tags/cost.md>), [cs-ai](<https://devfeed.tech/tags/cs-ai.md>), [cs-cl](<https://devfeed.tech/tags/cs-cl.md>), [experiments](<https://devfeed.tech/tags/experiments.md>), [exploration](<https://devfeed.tech/tags/exploration.md>), [fine-tuning](<https://devfeed.tech/tags/fine-tuning.md>), [inference](<https://devfeed.tech/tags/inference.md>), [information](<https://devfeed.tech/tags/information.md>), [llm](<https://devfeed.tech/tags/llm.md>), [llm-agents](<https://devfeed.tech/tags/llm-agents.md>), [models](<https://devfeed.tech/tags/models.md>), [performance](<https://devfeed.tech/tags/performance.md>), [qa](<https://devfeed.tech/tags/qa.md>), [question](<https://devfeed.tech/tags/question.md>), [repository](<https://devfeed.tech/tags/repository.md>), [score](<https://devfeed.tech/tags/score.md>), [tool](<https://devfeed.tech/tags/tool.md>), [tool-calling](<https://devfeed.tech/tags/tool-calling.md>)

### AI overview

JET trains repository question-answering agents to stop exploring once they have enough information. It truncates training trajectories at that point, adds a rationale explaining why an answer is justified, and gives that rationale higher loss weight. Across two repository QA benchmarks and two open-weight 8B models, JET reduced tool calls by 11-33% on self-generated trajectories while largely preserving scores. On expert trajectories, it used 18-28% fewer calls than SFT while retaining most of SFT's score gain. The abstract also reports lower inference cost in both settings.

### Source excerpt

arXiv:2611.22539v1 Announce Type: cross Abstract: In repository-level question answering (QA), an agent explores a code repository with tools and should answer a question once enough information is gathered. Nevertheless, we find that LLM agents often continue to invoke tools even after the gathered information is already sufficient to answer. We call this phenomenon over-exploration. Moreover, even though existing methods improve task performance through supervised fine-tuning (SFT) on expert trajectories, SFT also propagates the over-exploration in the trajectories to the agent. To mitigate over-exploration, we propose Just-Enough Exploration Tuning (JET), a fine-tuning method that trains the agent to answer once the gathered information is sufficient. JET truncates each training trajectory at the step where the gathered information becomes sufficient, inserts a rationale that explains why the agent can answer at that step, and fine-tunes the agent with a higher loss weight on the rationale. Experiments on two repository-level QA benchmarks with two open-weight 8B models demonstrate that JET reduces tool calls by 11 to 33% on self-generated trajectories while largely preserving the score. On expert trajectories, JET makes 18 to 28% fewer tool calls than SFT while retaining most of the score gain of SFT. In both cases, JET also lowers the inference cost.

## Track Copilot code review outcomes in Repository insights

DevFeed: [Track Copilot code review outcomes in Repository insights](<https://devfeed.tech/articles/track-copilot-code-review-outcomes-in-repository-insights-139404.md>)

Original publisher: [Read original article](<https://github.blog/changelog/2026-11-17-track-copilot-code-review-outcomes-in-repository-insights>)

Author: Allison

Published: 2026-11-17T18:00:35Z

Content type: release

Language: en

Sources: [GitHub Changelog](<https://devfeed.tech/sources/github-changelog.md>)

Topics: [ai code review](<https://devfeed.tech/topics/ai-code-review.md>), [Code review](<https://devfeed.tech/topics/code-review.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [Repository](<https://devfeed.tech/topics/repository.md>)

Tags: [account-management](<https://devfeed.tech/tags/account-management.md>), [api](<https://devfeed.tech/tags/api.md>), [billing](<https://devfeed.tech/tags/billing.md>), [categories](<https://devfeed.tech/tags/categories.md>), [code-review](<https://devfeed.tech/tags/code-review.md>), [copilot](<https://devfeed.tech/tags/copilot.md>), [copilot-code](<https://devfeed.tech/tags/copilot-code.md>), [coverage](<https://devfeed.tech/tags/coverage.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [enterprise-management-tools](<https://devfeed.tech/tags/enterprise-management-tools.md>), [feedback](<https://devfeed.tech/tags/feedback.md>), [insights](<https://devfeed.tech/tags/insights.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [pull-request](<https://devfeed.tech/tags/pull-request.md>), [pull-requests](<https://devfeed.tech/tags/pull-requests.md>), [release](<https://devfeed.tech/tags/release.md>), [reports](<https://devfeed.tech/tags/reports.md>), [repositories](<https://devfeed.tech/tags/repositories.md>), [repository](<https://devfeed.tech/tags/repository.md>), [request](<https://devfeed.tech/tags/request.md>), [review](<https://devfeed.tech/tags/review.md>), [reviews](<https://devfeed.tech/tags/reviews.md>), [types](<https://devfeed.tech/tags/types.md>)

### AI overview

Repository insights adds a page in each repository's Insights tab that summarizes Copilot code review outcomes: comments and high-severity comments addressed, reviewed pull requests without a later human change request, and merged pull requests that lacked Copilot review. It also provides the addressed rate with its numerator, denominator, unevaluable exclusions, trend, and supported breakdowns, plus comment categories. The same metrics are available in enterprise and organization `repos-1-day` reports through the Copilot usage metrics API. Repository viewers can access the page; API reports require an eligible owner, billing manager, or custom role with `View Copilot Metrics`. The Copilot usage metrics policy must be enabled.

### Source excerpt

You can now see how Copilot code review feedback lands in each repository. A new "Repository insights" page, the first item in a repository's Insights tab, brings Copilot code review... The post Track Copilot code review outcomes in Repository insights appeared first on The GitHub Blog.

## Gitea 28.4.0 is released

DevFeed: [Gitea 28.4.0 is released](<https://devfeed.tech/articles/gitea-28-4-0-is-released-135226.md>)

Original publisher: [Read original article](<https://blog.gitea.com/release-of-28.4.0/>)

Author: bircni

Published: 2026-11-15T21:00:00Z

Content type: release

Language: en

Sources: [Gitea Blog](<https://devfeed.tech/sources/gitea-blog.md>)

Topics: [Gitea](<https://devfeed.tech/topics/gitea.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [branch protection rules](<https://devfeed.tech/topics/branch-protection-rules.md>), [Repository](<https://devfeed.tech/topics/repository.md>)

Tags: [actions](<https://devfeed.tech/tags/actions.md>), [bug-fixes](<https://devfeed.tech/tags/bug-fixes.md>), [gitea](<https://devfeed.tech/tags/gitea.md>), [maintenance](<https://devfeed.tech/tags/maintenance.md>), [packages](<https://devfeed.tech/tags/packages.md>), [pull-requests](<https://devfeed.tech/tags/pull-requests.md>), [release](<https://devfeed.tech/tags/release.md>), [repositories](<https://devfeed.tech/tags/repositories.md>), [security-fixes](<https://devfeed.tech/tags/security-fixes.md>), [upgrade](<https://devfeed.tech/tags/upgrade.md>)

### AI overview

Gitea 28.4.0 is a security-focused maintenance release for the 28 series, with 41 merged pull requests. It closes vulnerabilities including command execution during repository auto-initialization, exposure of repository owners' password hashes through search, attachment deletion beyond a user's access, and failures to enforce protected file patterns for specially named files. Other fixes address access control across issues, pull requests, packages, tokens and Git LFS, plus Actions, API behavior, repositories and registries. The release binaries use Go 1.27.4, which fixes an HTTP/1 server crash and issues relevant when building untrusted code. Gitea recommends upgrading as soon as possible; the supplied text points users to its downloads and installation documentation.

### Source excerpt

We are excited to announce the release of **Gitea 28.4.0**, the fourth maintenance release for the 28 series. It contains a number of security fixes, among them fixes for command execution through repository auto-initialization and for the disclosure of password hashes through the repository search, and bug fixes for Actions, issues, pull requests, repositories and packages. We strongly recommend that all users upgrade as soon as possible.

## How I Built a Data-Driven Portfolio That Takes 30 Seconds to Update

DevFeed: [How I Built a Data-Driven Portfolio That Takes 30 Seconds to Update](<https://devfeed.tech/articles/how-i-built-a-data-driven-portfolio-that-takes-30-seconds-to-update-131610.md>)

Original publisher: [Read original article](<https://hackernoon.com/how-i-built-a-data-driven-portfolio-that-takes-30-seconds-to-update?source=rss>)

Author: sammii

Published: 2026-11-13T05:30:03Z

Content type: tutorial

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [JSON](<https://devfeed.tech/topics/json.md>), [Repository](<https://devfeed.tech/topics/repository.md>), [Tool](<https://devfeed.tech/topics/tool.md>)

Tags: [account](<https://devfeed.tech/tags/account.md>), [app](<https://devfeed.tech/tags/app.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [array](<https://devfeed.tech/tags/array.md>), [article](<https://devfeed.tech/tags/article.md>), [articles](<https://devfeed.tech/tags/articles.md>), [assets](<https://devfeed.tech/tags/assets.md>), [async](<https://devfeed.tech/tags/async.md>), [async-programming](<https://devfeed.tech/tags/async-programming.md>), [automated-portfolio](<https://devfeed.tech/tags/automated-portfolio.md>), [automatically](<https://devfeed.tech/tags/automatically.md>), [await](<https://devfeed.tech/tags/await.md>), [build](<https://devfeed.tech/tags/build.md>), [changes](<https://devfeed.tech/tags/changes.md>), [component](<https://devfeed.tech/tags/component.md>), [content-creation](<https://devfeed.tech/tags/content-creation.md>), [data](<https://devfeed.tech/tags/data.md>), [data-driven](<https://devfeed.tech/tags/data-driven.md>), [data-science](<https://devfeed.tech/tags/data-science.md>), [databases](<https://devfeed.tech/tags/databases.md>), [design](<https://devfeed.tech/tags/design.md>), [frontend-development](<https://devfeed.tech/tags/frontend-development.md>), [image](<https://devfeed.tech/tags/image.md>), [json](<https://devfeed.tech/tags/json.md>), [layout](<https://devfeed.tech/tags/layout.md>), [portfolio](<https://devfeed.tech/tags/portfolio.md>), [project](<https://devfeed.tech/tags/project.md>), [react-project-cards](<https://devfeed.tech/tags/react-project-cards.md>)

### AI overview

The portfolio renders project cards from a `projects.js` array, so adding a project requires no component, route, or layout changes. Each entry has four fields; its `id` also supplies the GitHub URL path, image lookup key, and React key. A build script scans the image folder and generates an extension map, while a utility uses the project ID's final path segment to find the image. The same project data feeds a responsive grid with expandable modals and a full-screen vertical carousel. The stated workflow is to add a screenshot, regenerate the image map, add a four-line project entry, and push. The author presents separating data from presentation as a pattern also used for article and account configuration in other products.

### Source excerpt

Adding a new project to my portfolio takes 30 seconds. No component changes. No new routes. No layout adjustments. Just 4 lines of JSON and an image dropped ...

## Multi-Repository Security Analysis with CodeRabbit Secure

DevFeed: [Multi-Repository Security Analysis with CodeRabbit Secure](<https://devfeed.tech/articles/multi-repository-security-analysis-with-coderabbit-secure-126472.md>)

Original publisher: [Read original article](<https://coderabbit.ai/blog/multi-repository-security-analysis-with-coderabbit-secure>)

Author: Konrad Sopala

Published: 2026-11-10T12:00:00Z

Content type: article

Language: en

Sources: [CodeRabbit](<https://devfeed.tech/sources/coderabbit.md>)

Topics: [code security](<https://devfeed.tech/topics/code-security.md>), [Static code analysis](<https://devfeed.tech/topics/static-code-analysis.md>), [Multi Agent Systems](<https://devfeed.tech/topics/multi-agent-systems.md>), [Secure token management](<https://devfeed.tech/topics/secure-token-management.md>), [Repository](<https://devfeed.tech/topics/repository.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [api](<https://devfeed.tech/tags/api.md>), [api-gateway](<https://devfeed.tech/tags/api-gateway.md>), [application](<https://devfeed.tech/tags/application.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [assessment](<https://devfeed.tech/tags/assessment.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [bootstrap](<https://devfeed.tech/tags/bootstrap.md>), [branch](<https://devfeed.tech/tags/branch.md>), [bypass](<https://devfeed.tech/tags/bypass.md>), [charts](<https://devfeed.tech/tags/charts.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [context](<https://devfeed.tech/tags/context.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [english](<https://devfeed.tech/tags/english.md>), [featured](<https://devfeed.tech/tags/featured.md>), [repositories](<https://devfeed.tech/tags/repositories.md>), [repository](<https://devfeed.tech/tags/repository.md>), [scan](<https://devfeed.tech/tags/scan.md>), [security](<https://devfeed.tech/tags/security.md>), [security-analysis](<https://devfeed.tech/tags/security-analysis.md>)

### AI overview

CodeRabbit Secure's Deep Scan can use linked repositories as read-only context to trace settings, shared code, and deployment configuration while investigating findings in a primary repository. Architecture summaries and auto-linking help identify related repositories; teams can also configure links and source access. Agents use this context across recon, hunt, and verify, but linked repositories receive no findings or coverage from that scan and require separate scans. In two open-source experiments, linked startup code clarified that default administrator credentials applied during fresh installation, while a runtime check showed changing the bootstrap password did not rotate an existing account's password. In another experiment, supplying the runtime repository let the evaluator distinguish enabled from disabled reload configurations; the chart alone left both unresolved. Linked source is pinned to the default branch commit, which may differ from deployed code. Manual mode reads selected repositories; automatic mode reads eligible linked repositories up to the plan limit until the source list is customized. Supported platforms listed are GitHub Cloud, GitHub Enterprise Server, 

### Source excerpt

An application can have an authentication check and still expose data if a caller can bypass the service that enforces it. Multi-repository analysis in CodeRabbit Secure gives Deep Scan agents read-only context from linked repositories, so they can follow a configuration value, shared library, or deployment setting to the code that consumes it while investigating a finding.

## SWE-Time: Benchmarking Temporal Repository Understanding

DevFeed: [SWE-Time: Benchmarking Temporal Repository Understanding](<https://devfeed.tech/articles/swe-time-benchmarking-temporal-repository-understanding-127261.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.12083>)

Author: Shijun Xiao, Xinrong Chen, Hao Liu, Wensheng Zhang, Yongqiang Tang

Published: 2026-11-10T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [code search](<https://devfeed.tech/topics/code-search.md>), [Repository](<https://devfeed.tech/topics/repository.md>), [versioning](<https://devfeed.tech/topics/versioning.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [benchmark](<https://devfeed.tech/tags/benchmark.md>), [benchmarking](<https://devfeed.tech/tags/benchmarking.md>), [benchmarks](<https://devfeed.tech/tags/benchmarks.md>), [coding-agents](<https://devfeed.tech/tags/coding-agents.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [developer](<https://devfeed.tech/tags/developer.md>), [evaluation](<https://devfeed.tech/tags/evaluation.md>), [evolution](<https://devfeed.tech/tags/evolution.md>), [framework](<https://devfeed.tech/tags/framework.md>), [github](<https://devfeed.tech/tags/github.md>), [regression](<https://devfeed.tech/tags/regression.md>), [repository](<https://devfeed.tech/tags/repository.md>), [retrospective](<https://devfeed.tech/tags/retrospective.md>), [temporal](<https://devfeed.tech/tags/temporal.md>), [time](<https://devfeed.tech/tags/time.md>)

### AI overview

SWE-Time evaluates code agents on repository evolution rather than treating repositories as static snapshots. It tests retrospective understanding through historical regression analysis and prospective understanding of intended changes from pre-change states, using a framework that turns real developer queries and historical evidence into verifiable tasks. Across 1,661 cases from 65 GitHub repositories, 15 coding agents were evaluated; within Claude Code, Claude Opus 4.8 scored highest, with a SWE-Time average of 61.9. The abstract reports that historical code evidence and developer intent matter, while reasoning consistently across repository states remains challenging.

### Source excerpt

arXiv:2611.12083v1 Announce Type: new Abstract: Repository-level code-understanding benchmarks have progressively expanded the spatial scope of reasoning, from local code to entire repositories, while largely treating each repository as a static snapshot. However, how models reason about repository evolution over time remains largely unexplored. We introduce SWE-Time, a benchmark for temporal repository understanding that makes repository evolution itself the reasoning target. SWE-Time evaluates two complementary temporal directions: retrospective understanding of repository evolution through historical regression analysis and prospective understanding of intended changes from pre-change repository states. To enable realistic yet reliable evaluation in these settings, we introduce the RealWorld-to-Verifiable Construction Framework, which transforms real-world developer queries and historical evidence into verifiable evaluation tasks. We evaluate 15 coding agents on 1,661 cases from 65 GitHub repositories. Within Claude Code, Claude Opus 4.8 achieves the highest SWE-Time Avg. of 61.9, leaving substantial headroom. Controlled analyses highlight the importance of historical code evidence and developer intent, while consistent reasoning across repository states remains challenging. These results highlight repository evolution as a distinct and challenging dimension of code understanding.

## F3D updated, now supports FreeCAD files!

DevFeed: [F3D updated, now supports FreeCAD files!](<https://devfeed.tech/articles/f3d-updated-now-supports-freecad-files-121626.md>)

Original publisher: [Read original article](<https://blog.adafruit.com/2026/11/06/f3d-updated-now-supports-freecad-files/>)

Author: Anne Barela

Published: 2026-11-06T21:08:02Z

Content type: release

Language: en

Sources: [Adafruit Industries](<https://devfeed.tech/sources/adafruit-industries-makers-hackers-artists-designers-and-engineers.md>)

Topics: [3D](<https://devfeed.tech/topics/3d.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>), [Repository](<https://devfeed.tech/topics/repository.md>)

Tags: [3d](<https://devfeed.tech/tags/3d.md>), [3d-model](<https://devfeed.tech/tags/3d-model.md>), [3d-printing](<https://devfeed.tech/tags/3d-printing.md>), [animation](<https://devfeed.tech/tags/animation.md>), [f3d](<https://devfeed.tech/tags/f3d.md>), [freecad](<https://devfeed.tech/tags/freecad.md>), [generate](<https://devfeed.tech/tags/generate.md>), [hosting](<https://devfeed.tech/tags/hosting.md>), [local](<https://devfeed.tech/tags/local.md>), [manyfold](<https://devfeed.tech/tags/manyfold.md>), [open](<https://devfeed.tech/tags/open.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [preview](<https://devfeed.tech/tags/preview.md>), [web](<https://devfeed.tech/tags/web.md>)

### AI overview

F3D 4.0 can open FreeCAD FCStd files. Its public web viewer can load a sample or a local file and offers controls for lighting, positioning, animation playback, and video creation; installable packages are available for many operating systems. FreeCAD uses F3D to generate STEP thumbnails, and Manyfold's latest release renders previews of FreeCAD files by default. The excerpt does not provide further details about file support or rendering limitations.

### Source excerpt

Jo Hinchliffe writes on the FreeCAD blog that F3D, the open source 3D model renderer and viewer, can now open FreeCAD FCStd files as of version 4.0. The simplest way to try it is the public web viewer, which loads a sample file or a file from the local machine. There's more to it than [...]

## A Low Similarity Score Does Not Show Independence after Source-Conditioned Repository Rewriting

DevFeed: [A Low Similarity Score Does Not Show Independence after Source-Conditioned Repository Rewriting](<https://devfeed.tech/articles/a-low-similarity-score-does-not-show-independence-after-source-conditioned-repository-rewriting-120828.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.07887>)

Author: Micheline B\\'en\\'edicte Moumoula, Serge Lionel Nikiema, Tailia Malloy, Abdoul Kader Kabor\\'e, Jacques Klein, Tegawend\\'e F. Bissyande

Published: 2026-11-06T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [Open Source](<https://devfeed.tech/topics/open-source.md>), [Test automation](<https://devfeed.tech/topics/test-automation.md>), [Repository](<https://devfeed.tech/topics/repository.md>)

Tags: [abstract](<https://devfeed.tech/tags/abstract.md>), [agent](<https://devfeed.tech/tags/agent.md>), [arxiv](<https://devfeed.tech/tags/arxiv.md>), [based](<https://devfeed.tech/tags/based.md>), [better](<https://devfeed.tech/tags/better.md>), [can](<https://devfeed.tech/tags/can.md>), [candidate](<https://devfeed.tech/tags/candidate.md>), [code](<https://devfeed.tech/tags/code.md>), [coding](<https://devfeed.tech/tags/coding.md>), [coding-agent](<https://devfeed.tech/tags/coding-agent.md>), [copy](<https://devfeed.tech/tags/copy.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [effects](<https://devfeed.tech/tags/effects.md>), [fall](<https://devfeed.tech/tags/fall.md>), [fingerprint](<https://devfeed.tech/tags/fingerprint.md>), [fixed](<https://devfeed.tech/tags/fixed.md>), [repository](<https://devfeed.tech/tags/repository.md>), [score](<https://devfeed.tech/tags/score.md>), [show](<https://devfeed.tech/tags/show.md>), [similarity](<https://devfeed.tech/tags/similarity.md>), [source](<https://devfeed.tech/tags/source.md>)

### AI overview

In 69 agent-only rewrites of six copyleft Python projects, a low JPlag similarity score from one run was weak evidence of independence. Agents retained the original in their working copies and iterated until a behavioral harness passed; every rewrite passed after repair, usually within half an hour for the initial rewrite. Under a ground-up rearchitecture prompt, most rewrites scored below 25%. But identical project, agent, and prompt setups produced wide score variation, and more than a third of configurations had three repeats on both sides of the threshold. Imports and fingerprint facts also failed to distinguish rewrites from hand-written independent implementations of the same task better than chance. The authors recommend reporting repeated generations and validating provenance signals against same-task independent implementations, not only unrelated projects. The evidence covers six Python projects and 69 rewrites.

### Source excerpt

arXiv:2611.07887v1 Announce Type: new Abstract: Maintainers sometimes cite a low token-similarity score as evidence that an LLM-assisted rewrite of a copyleft project is independent of the original. We test what such a score can support under \emph{source-conditioned} rewriting: a coding agent keeps the original in its working copy, rewrites the repository, and iterates until a fixed behavioural harness passes, with no human edit to the code. On 69 rewrites of six copyleft Python projects we find that: \ding{182}~Agent-only rewriting is inexpensive and often yields low scores. Every controlled rewrite passes the harness after repair, usually within half an hour for the initial rewrite. Under a ground-up rearchitecture prompt, most rewrites fall below 25\% JPlag similarity and still pass the harness. \ding{183}~A single low score is an unreliable witness. Identical project--agent--prompt configurations produce wide spreads in similarity; run-to-run variation dominates project and agent effects, and in more than a third of configurations the three repeats straddle the threshold. Rewrites retain more of the original's imports and fingerprint facts than unrelated projects do, yet hand-written independent implementations of the same task often retain as much, and neither signal separates the two groups better than chance. Thus a low score on one rewrite is weak evidence of independence: another run of the same agent may score high. Claims based on similarity should report repeated generations, and candidate provenance signals should be checked against same task independent implementations, not only against unrelated projects.

## Repository and Issue Characteristics of Early GenAI Adopters on GitHub

DevFeed: [Repository and Issue Characteristics of Early GenAI Adopters on GitHub](<https://devfeed.tech/articles/repository-and-issue-characteristics-of-early-genai-adopters-on-github-116169.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2607.21079>)

Author: Rikuto Tsuchida, Youmei Fan, Kazumasa Shimari, Raula Gaikovina Kula, Gema Rodr\\'iguez-P\\'erez, Kenichi Matsumoto

Published: 2026-11-04T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [AI-assisted coding](<https://devfeed.tech/topics/ai-assisted-coding.md>), [Repository](<https://devfeed.tech/topics/repository.md>), [GitHub Issues](<https://devfeed.tech/topics/github-issues.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [2025](<https://devfeed.tech/tags/2025.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-assistance](<https://devfeed.tech/tags/ai-assistance.md>), [ai-assistants](<https://devfeed.tech/tags/ai-assistants.md>), [ai-tool](<https://devfeed.tech/tags/ai-tool.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [autonomous-ai-agents](<https://devfeed.tech/tags/autonomous-ai-agents.md>), [blocks](<https://devfeed.tech/tags/blocks.md>), [code](<https://devfeed.tech/tags/code.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [data](<https://devfeed.tech/tags/data.md>), [developers](<https://devfeed.tech/tags/developers.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [genai](<https://devfeed.tech/tags/genai.md>), [github](<https://devfeed.tech/tags/github.md>), [issue](<https://devfeed.tech/tags/issue.md>), [repository](<https://devfeed.tech/tags/repository.md>)

### AI overview

The study found modest README differences between GitHub repositories with AI-tool configuration files (ACFs) and matched repositories without them: ACF repositories had longer READMEs, more code blocks, and more often included a license; repositories without ACFs had more external URLs. Category distributions differed only weakly, and issue Type and Outcome showed no difference once GenAI relatedness was held fixed. The analysis covered 531 early adopters, 100 ACF repositories, 100 matched controls, and 370 issues, using data collected from May to August 2025.

### Source excerpt

arXiv:2607.21079v2 Announce Type: replace Abstract: Generative artificial intelligence (GenAI) has introduced new forms of AI assistance into software development, but less is known about the repositories and issues of early adopters of GenAI tools. We study the repository and issue characteristics of early adopters who state interest in GenAI on their public profiles on GitHub by analyzing 531 early adopters, 100 of their repositories with AI-tool configuration files (ACFs), 100 matched control repositories without ACFs, and 370 issues from the two repository groups. Repositories with ACFs show modest distributional differences in selected README structural characteristics. They contain longer README files with more code blocks and include a license more often, while repositories without ACFs contain more external URLs. The category distributions of the two repository groups show weak evidence of a difference. Once GenAI relatedness is held fixed, we detect no difference in issue Type or Outcome between the two repository groups. Our data, collected from May to August 2025, record how early adopters developed software in Software Engineering 2.0, the stage in which developers use both AI assistants and autonomous AI agents. When these agents become the norm, later studies can compare their data with ours.

## Launder-Bench: Can Repository-Level Agentic Code Laundering Be Detected?

DevFeed: [Launder-Bench: Can Repository-Level Agentic Code Laundering Be Detected?](<https://devfeed.tech/articles/launder-bench-can-repository-level-agentic-code-laundering-be-detected-113516.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.01966>)

Author: Yuntong Hu, Hongji Pu, Zimo Li, Ruomeng Li, Xiaotong Liu, Ziyuan Qin, Qiyue Li, Liang Zhao

Published: 2026-11-03T05:00:00Z

Content type: news

Language: en

Sources: [arXiv: Artificial Intelligence](<https://devfeed.tech/sources/arxiv-artificial-intelligence.md>), [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [agentic-coding](<https://devfeed.tech/topics/agentic-coding.md>), [Refactoring](<https://devfeed.tech/topics/refactoring.md>), [code analysis](<https://devfeed.tech/topics/code-analysis.md>), [Repository](<https://devfeed.tech/topics/repository.md>), [reproducibility](<https://devfeed.tech/topics/reproducibility.md>)

Tags: [agentic](<https://devfeed.tech/tags/agentic.md>), [auditing](<https://devfeed.tech/tags/auditing.md>), [bench](<https://devfeed.tech/tags/bench.md>), [benchmark](<https://devfeed.tech/tags/benchmark.md>), [clone](<https://devfeed.tech/tags/clone.md>), [code](<https://devfeed.tech/tags/code.md>), [coding-agents](<https://devfeed.tech/tags/coding-agents.md>), [cs-ai](<https://devfeed.tech/tags/cs-ai.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [detection](<https://devfeed.tech/tags/detection.md>), [domain](<https://devfeed.tech/tags/domain.md>), [hidden](<https://devfeed.tech/tags/hidden.md>), [independent](<https://devfeed.tech/tags/independent.md>), [modules](<https://devfeed.tech/tags/modules.md>), [pair](<https://devfeed.tech/tags/pair.md>), [provenance](<https://devfeed.tech/tags/provenance.md>), [real-world](<https://devfeed.tech/tags/real-world.md>), [repository](<https://devfeed.tech/tags/repository.md>), [rewrite](<https://devfeed.tech/tags/rewrite.md>), [similarity](<https://devfeed.tech/tags/similarity.md>), [static](<https://devfeed.tech/tags/static.md>), [verification](<https://devfeed.tech/tags/verification.md>)

### AI overview

Launder-Bench tests whether repository-scale code rewrites that preserve behavior can be traced to their source. Built from 282 repositories, it uses source-hidden reconstruction and execution-based verification, with 1,128 pairwise provenance cases and 229 source-attribution cases that allow abstention. Same-domain independent repositories provide reference bands for similarity without shared provenance. Existing methods perform poorly: the strongest static method reaches 0.66 AUROC on pairwise detection; repository encoders rank the true source first in up to 22% of attribution queries, but receive calibrated attribution credit in only 1-2%. The results show that ranking a similar repository does not by itself establish provenance.

### Source excerpt

arXiv:2611.01966v1 Announce Type: new Abstract: Coding agents can now rewrite repository-scale codebases while preserving tested behavior, creating a new challenge for plagiarism detection, license auditing, and software provenance. We ask whether such rewrites can still be traced to their source. Existing clone benchmarks emphasize fragments and bounded edits, while repository-transformation benchmarks evaluate functional correctness rather than provenance. Moreover, ranking the most similar source does not establish derivation when independent implementations can be similarly close. We define repository-level agentic code laundering and introduce Launder-Bench, to our knowledge the first repository-level benchmark for provenance under agentic rewriting, constructed from 282 real-world repositories. A source-hidden reconstruction protocol decomposes source behavior, reconstructs modules and repository structure, and retains rewrites only after execution-based verification. We evaluate the same provenance problem in two complementary settings: Launder-Bench-Pair contains 1,128 pairwise instances asking whether two repositories share provenance, while Launder-Bench-Attr contains 229 source-attribution instances asking which candidate is the source, with abstention when evidence is insufficient. Measured same-domain independent repositories establish how much similarity can arise without shared provenance and provide detector-specific reference bands. Existing methods remain far from saturating Launder-Bench: the strongest static method reaches only 0.66 AUROC on pairwise detection, while repository encoders rank the true source first on up to 22% of attribution queries but earn calibrated attribution credit on only 1-2%. These results reveal a systematic gap between relative code similarity and source-specific provenance evidence, providing a reproducible target for provenance detection under agentic rewriting.

## CrossSWE: Benchmarking Cross-Repository Joint Development for Coding Agents

DevFeed: [CrossSWE: Benchmarking Cross-Repository Joint Development for Coding Agents](<https://devfeed.tech/articles/crossswe-benchmarking-cross-repository-joint-development-for-coding-agents-113509.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.01484>)

Author: Silin Chen, Yuling Shi, Heng Lian, Zihan Zhang, Xiaodong Gu, Haotian Lin, Zhensu Sun

Published: 2026-11-03T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [Software Engineering](<https://devfeed.tech/topics/software-engineering.md>), [agentic-coding](<https://devfeed.tech/topics/agentic-coding.md>), [AI-assisted coding](<https://devfeed.tech/topics/ai-assisted-coding.md>), [Repository](<https://devfeed.tech/topics/repository.md>), [Programming](<https://devfeed.tech/topics/programming.md>)

Tags: [benchmarking](<https://devfeed.tech/tags/benchmarking.md>), [benchmarks](<https://devfeed.tech/tags/benchmarks.md>), [challenges](<https://devfeed.tech/tags/challenges.md>), [coding-agents](<https://devfeed.tech/tags/coding-agents.md>), [consistency](<https://devfeed.tech/tags/consistency.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [dependency](<https://devfeed.tech/tags/dependency.md>), [evaluation](<https://devfeed.tech/tags/evaluation.md>), [failure](<https://devfeed.tech/tags/failure.md>), [languages](<https://devfeed.tech/tags/languages.md>), [llms](<https://devfeed.tech/tags/llms.md>), [repositories](<https://devfeed.tech/tags/repositories.md>), [software-development](<https://devfeed.tech/tags/software-development.md>)

### AI overview

CrossSWE tests whether coding agents can coordinate changes across interdependent repositories: its 171 real-world instances span 165 repositories, 20 technical domains and 13 programming languages, and require coordinated modifications because partial changes do not achieve the intended behavior. In evaluations of five LLMs, GPT-6.1 Sol scored the highest Pass@1 at 58.48%. Cross-repository inconsistencies were the most common failure mode, accounting for 44.2%.

### Source excerpt

arXiv:2611.01484v1 Announce Type: new Abstract: As coding agents achieve increasingly high success rates on software engineering benchmarks, recent efforts have sought to increase task complexity through longer horizons and more extensive code modifications. However, real-world software development often spans multiple interdependent repositories, introducing additional challenges in dependency reasoning, change propagation, and interface consistency. Rather than further increasing complexity within individual repositories, we introduce CrossSWE, a benchmark for cross-repository joint development comprising 171 real-world instances spanning 165 repositories, 20 technical domains, and 13 programming languages. CrossSWE verifies the necessity of coordinated changes by testing whether partial repository modifications are insufficient to achieve the intended behavior. Our evaluation of five LLMs reveals substantial challenges, with the strongest model, GPT-6.1 Sol, achieving only 58.48% Pass@1. Furthermore, cross-repository inconsistencies emerge as the most prevalent failure mode (44.2%), highlighting the difficulty of maintaining consistency across interdependent repositories.

## Introducing Svet: A Git Repository Linter

DevFeed: [Introducing Svet: A Git Repository Linter](<https://devfeed.tech/articles/introducing-svet-a-git-repository-linter-110590.md>)

Original publisher: [Read original article](<https://code.dblock.org/2026/10/31/introducing-svet-a-git-repository-linter.html>)

Author: Daniel Doubrovkine (dblock@dblock.org)

Published: 2026-10-31T00:00:00Z

Content type: release

Language: en

Sources: [Daniel Doubrovkine](<https://devfeed.tech/sources/daniel-doubrovkine.md>)

Topics: [lint](<https://devfeed.tech/topics/lint.md>), [Git](<https://devfeed.tech/topics/git.md>), [ESLint](<https://devfeed.tech/topics/eslint.md>), [Repository](<https://devfeed.tech/topics/repository.md>), [Tool](<https://devfeed.tech/topics/tool.md>), [Prettier](<https://devfeed.tech/topics/prettier.md>)

Tags: [eslint](<https://devfeed.tech/tags/eslint.md>), [git](<https://devfeed.tech/tags/git.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [lint](<https://devfeed.tech/tags/lint.md>), [linter](<https://devfeed.tech/tags/linter.md>), [nodejs](<https://devfeed.tech/tags/nodejs.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [plugin](<https://devfeed.tech/tags/plugin.md>), [portable](<https://devfeed.tech/tags/portable.md>), [pre-commit](<https://devfeed.tech/tags/pre-commit.md>), [repository](<https://devfeed.tech/tags/repository.md>), [testing](<https://devfeed.tech/tags/testing.md>)

### AI overview

Svet is a JavaScript repository linter that separates file selection from checks, so checks can use both file contents and Git path metadata without requiring a language parser. Its default Git selector checks tracked text files for LF endings and includes binary paths in the inventory used for filename checks. The `--precommit` mode checks staged Git-index snapshots without staging, stashing, or fixing files; revision comparisons use target-commit contents and do not fetch branches. Separate plugins provide checks such as trailing whitespace and path case. The excerpt contrasts this with an ESLint portability plugin that detects case and Unicode-normalization collisions, Windows-invalid names, and configurable path-length limits, but sees the current filesystem rather than staged snapshots and cannot fix filesystem names.

### Source excerpt

The idea for Svet came from a private repository at work, where checking filename case helps catch portability problems like Logo.svg and logo.svg colliding on a case-insensitive Windows filesystem. These checks are implemented in pure JavaScript. That seemed like a useful job for a reusable repository linter. I went looking for an existing tool. Tool Why it isn't enough here ESLint Can check filenames with a processor; byte-level checks and Git snapshots need custom plumbing. Oxlint Arbitrary non-JS/TS files don't reach its lint rules. Biome Checks supported languages, not arbitrary repository files. Stylelint Built for stylesheet rules; repository-wide checks need custom code. markdownlint-cli2 Can check filenames, but Markdown parsing isn't a byte-level checking API. HTML-validate Requires HTML or template transformations, not a general file-checking API. Prettier Skips or rejects unsupported formats; doesn't check repository-wide path rules. lint-staged Can run the checks, but doesn't supply rules or Git-index snapshots itself. Prettier is a formatter, and lint-staged is a task runner. They're in this list because they also appear in development and CI workflows. The important distinction is selecting a path, checking its name, understanding its contents, and choosing which version of those contents to inspect. Those are four different things. I built Svet for that job. Then I doubted myself and took a detour extending ESLint with eslint-plugin-portable-paths. It checks four portability problems: case-insensitive file and directory collisions, Unicode-normalization collisions, Windows-invalid names such as NUL.txt, and paths or individual names exceeding configurable lengths. It's almost everything. The remaining limitations of the eslint approach are about which files and bytes we're checking. This plugin sees the current filesystem, including untracked paths, and is not Git-aware, so a pre-commit hook would check the working tree, not the staged snapshot. ESLi

## Repository plugin defaults and enterprise plugin controls generally available

DevFeed: [Repository plugin defaults and enterprise plugin controls generally available](<https://devfeed.tech/articles/repository-plugin-defaults-and-enterprise-plugin-controls-generally-available-106990.md>)

Original publisher: [Read original article](<https://github.blog/changelog/2026-10-28-repository-plugin-defaults-and-enterprise-plugin-controls-generally-available>)

Author: Allison

Published: 2026-10-28T15:33:00Z

Content type: news

Language: en

Sources: [GitHub Changelog](<https://devfeed.tech/sources/github-changelog.md>)

Topics: [Repository](<https://devfeed.tech/topics/repository.md>)

Tags: [administrator](<https://devfeed.tech/tags/administrator.md>), [app](<https://devfeed.tech/tags/app.md>), [automatically](<https://devfeed.tech/tags/automatically.md>), [block](<https://devfeed.tech/tags/block.md>), [business](<https://devfeed.tech/tags/business.md>), [cli](<https://devfeed.tech/tags/cli.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [contributors](<https://devfeed.tech/tags/contributors.md>), [copilot](<https://devfeed.tech/tags/copilot.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [github](<https://devfeed.tech/tags/github.md>), [github-copilot](<https://devfeed.tech/tags/github-copilot.md>), [github-copilot-app](<https://devfeed.tech/tags/github-copilot-app.md>), [improvement](<https://devfeed.tech/tags/improvement.md>), [install](<https://devfeed.tech/tags/install.md>), [managed](<https://devfeed.tech/tags/managed.md>), [plugin](<https://devfeed.tech/tags/plugin.md>), [plugins](<https://devfeed.tech/tags/plugins.md>), [repositories](<https://devfeed.tech/tags/repositories.md>), [repository](<https://devfeed.tech/tags/repository.md>), [universe26](<https://devfeed.tech/tags/universe26.md>), [vs-code](<https://devfeed.tech/tags/vs-code.md>)

### AI overview

Repository maintainers can define a plugin marketplace and default plugins so contributors avoid repeating project setup; contributors may turn off those defaults where policy permits. Enterprise administrators can approve marketplaces and require or block plugins through managed settings. Required plugins install and enable automatically and cannot be disabled by users, and managed settings take precedence over repository and personal choices. Repository defaults are available to individual Copilot users and users with Copilot Business or Enterprise. Managed controls are available on GitHub Enterprise Cloud for users whose Copilot Business or Enterprise licenses were issued by the enterprise or one of its organizations. The controls are available in VS Code, Copilot CLI, and the GitHub Copilot app.

### Source excerpt

Repository plugin defaults and enterprise-managed plugin controls are now generally available in VS Code, Copilot CLI, and the GitHub Copilot app. Trusted repositories can install and enable default plugins for... The post Repository plugin defaults and enterprise plugin controls generally available appeared first on The GitHub Blog.

## Your agent can now publish your docs

DevFeed: [Your agent can now publish your docs](<https://devfeed.tech/articles/your-agent-can-now-publish-your-docs-106831.md>)

Original publisher: [Read original article](<https://www.mintlify.com/blog/mint-deploy>)

Author: Denzell Ford

Published: 2026-10-28T00:00:00Z

Content type: release

Language: en

Sources: [Mintlify Blog](<https://devfeed.tech/sources/mintlify-blog.md>)

Topics: [Publishing](<https://devfeed.tech/topics/publishing.md>), [Claude Code](<https://devfeed.tech/topics/claude-code.md>), [npm](<https://devfeed.tech/topics/npm.md>), [Repository](<https://devfeed.tech/topics/repository.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [2026](<https://devfeed.tech/tags/2026.md>), [3](<https://devfeed.tech/tags/3.md>), [account](<https://devfeed.tech/tags/account.md>), [acme](<https://devfeed.tech/tags/acme.md>), [actions](<https://devfeed.tech/tags/actions.md>), [admin](<https://devfeed.tech/tags/admin.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-workflow](<https://devfeed.tech/tags/agentic-workflow.md>), [agents](<https://devfeed.tech/tags/agents.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [article](<https://devfeed.tech/tags/article.md>), [can](<https://devfeed.tech/tags/can.md>), [docs](<https://devfeed.tech/tags/docs.md>), [github](<https://devfeed.tech/tags/github.md>), [github-repository](<https://devfeed.tech/tags/github-repository.md>), [live](<https://devfeed.tech/tags/live.md>), [repository](<https://devfeed.tech/tags/repository.md>), [site](<https://devfeed.tech/tags/site.md>), [terminal](<https://devfeed.tech/tags/terminal.md>)

### AI overview

The `mint deploy` CLI lets agents publish a live Mintlify docs site without an account or GitHub repository: from the folder containing `docs.json`, run `npm i -g mint` and `mint deploy --subdomain acme`. It creates a hosted Git repository, pushes the docs, and serves the site at `acme.mintlify.site`. The owner must claim the site within 24 hours using an email, sign-in, and code exchange; an unclaimed first site is deleted with its repository when that period expires. For an existing GitHub repository, `mint deploy --github` sets up a GitHub Actions workflow for default-branch updates, but this option applies only before claiming. After claiming, GitHub can be connected in dashboard settings. Agents unable to install the CLI can use the `auth.md` raw HTTP flow.

### Source excerpt

Agents can publish a live Mintlify site from the terminal without an account or GitHub repository. You can claim the site within 24 hours.

## Rivet: Utility-Preserving Context Control for Repository-Level Coding Agents

DevFeed: [Rivet: Utility-Preserving Context Control for Repository-Level Coding Agents](<https://devfeed.tech/articles/rivet-utility-preserving-context-control-for-repository-level-coding-agents-101796.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2610.34967>)

Author: Ruwei Pan, Linhao Wu, Yakun Zhang, Zixiong Yang, Lu Zhang, Hongyu Zhang

Published: 2026-10-27T04:00:00Z

Content type: article

Language: en

Sources: [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [agentic-coding](<https://devfeed.tech/topics/agentic-coding.md>), [AI-assisted coding](<https://devfeed.tech/topics/ai-assisted-coding.md>), [Retrieval Augmented Generation (RAG)](<https://devfeed.tech/topics/retrieval-augmented-generation-rag.md>), [Repository](<https://devfeed.tech/topics/repository.md>)

Tags: [4k](<https://devfeed.tech/tags/4k.md>), [8k](<https://devfeed.tech/tags/8k.md>), [abstract](<https://devfeed.tech/tags/abstract.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [all](<https://devfeed.tech/tags/all.md>), [arxiv](<https://devfeed.tech/tags/arxiv.md>), [benchmarks](<https://devfeed.tech/tags/benchmarks.md>), [budget](<https://devfeed.tech/tags/budget.md>), [but](<https://devfeed.tech/tags/but.md>), [call](<https://devfeed.tech/tags/call.md>), [can](<https://devfeed.tech/tags/can.md>), [code](<https://devfeed.tech/tags/code.md>), [code-generation](<https://devfeed.tech/tags/code-generation.md>), [coding](<https://devfeed.tech/tags/coding.md>), [coding-agents](<https://devfeed.tech/tags/coding-agents.md>), [context](<https://devfeed.tech/tags/context.md>), [control](<https://devfeed.tech/tags/control.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [repository](<https://devfeed.tech/tags/repository.md>), [utility](<https://devfeed.tech/tags/utility.md>)

### AI overview

Rivet aims to prevent "context utility dilution": repository context can look task-relevant while omitting evidence needed to implement and integrate code. It selects code anchors using lexical, semantic, and structural signals, follows dependency, usage, and configuration links to gather related evidence, then prioritizes that evidence under a token budget, shortening snippets to signatures or summaries before dropping them. On DevEval and RepoExec, across four backbone models, 4K and 8K token budgets, and eight baselines, the abstract reports the highest Pass@1 in all 16 settings and a 3.73-5.15 percentage-point average gain over the strongest baseline. It also reports GPT-5-mini with Rivet outperforming GPT-5 without Rivet on both benchmarks while reducing inference cost by 73.3-84.5%. These are abstract-level reported results; the supplied text does not include evaluation details.

### Source excerpt

arXiv:2610.34967v1 Announce Type: new Abstract: Repository-level code generation asks an agent to implement a task requirement inside an existing repository. To produce code that works in the repository, the agent needs repository evidence, such as target locations, helper definitions, caller usages, and configuration constraints, which determine how the code should be located, integrated, and executed. Because the context budget cannot hold the entire repository, existing retrieval, compression, and structure-aware methods select context by task similarity, context length, or structural proximity, but these criteria do not directly measure whether the selected context contains this evidence. As a result, the selected context can appear relevant to the task yet miss the evidence that the implementation depends on. We call this failure mode context utility dilution. In this paper, we propose Rivet, a context control framework that preserves repository evidence for coding agents under a fixed context budget. Rivet, first uses Signal Grounding to select task-related code anchors by fusing lexical, semantic, and structural signals. Utility Linking then expands these anchors through dependency, usage, and configuration relations to collect repository evidence. Finally, Budget Shaping packs the evidence by priority and, when the budget is tight, reduces snippets to signatures or summaries before dropping them. We evaluate Rivet, on two executable repository-level benchmarks, DevEval and RepoExec, with four backbone models, two context budgets (4K and 8K tokens), and eight baselines. Rivet, achieves the highest Pass@1 in all 16 settings and improves over the strongest baseline by 3.73--5.15 percentage points on average. Moreover, GPT-5-mini with Rivet, outperforms GPT-5 without Rivet,on both benchmarks while reducing inference cost by 73.3%--84.5%.

## The token that never expired: What the Zeabur breach teaches SaaS teams that store customer secrets

DevFeed: [The token that never expired: What the Zeabur breach teaches SaaS teams that store customer secrets](<https://devfeed.tech/articles/the-token-that-never-expired-what-the-zeabur-breach-teaches-saas-teams-that-store-customer-secrets-102783.md>)

Original publisher: [Read original article](<https://workos.com/blog/zeabur-breach-customer-secrets>)

Author: WorkOS

Published: 2026-10-27T00:00:00Z

Content type: article

Language: en

Sources: [WorkOS](<https://devfeed.tech/sources/workos-blog.md>)

Topics: [Secrets Management](<https://devfeed.tech/topics/secrets-management.md>), [Secure token management](<https://devfeed.tech/topics/secure-token-management.md>), [Cryptography](<https://devfeed.tech/topics/cryptography.md>), [Post Mortem](<https://devfeed.tech/topics/post-mortem.md>), [Repository](<https://devfeed.tech/topics/repository.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [3](<https://devfeed.tech/tags/3.md>), [admin](<https://devfeed.tech/tags/admin.md>), [breach](<https://devfeed.tech/tags/breach.md>), [cluster](<https://devfeed.tech/tags/cluster.md>), [created](<https://devfeed.tech/tags/created.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [customer](<https://devfeed.tech/tags/customer.md>), [customers](<https://devfeed.tech/tags/customers.md>), [environment](<https://devfeed.tech/tags/environment.md>), [environment-variables](<https://devfeed.tech/tags/environment-variables.md>), [means](<https://devfeed.tech/tags/means.md>), [product](<https://devfeed.tech/tags/product.md>), [saas](<https://devfeed.tech/tags/saas.md>), [secrets](<https://devfeed.tech/tags/secrets.md>), [store](<https://devfeed.tech/tags/store.md>), [teams](<https://devfeed.tech/tags/teams.md>), [token](<https://devfeed.tech/tags/token.md>), [variables](<https://devfeed.tech/tags/variables.md>), [zeabur](<https://devfeed.tech/tags/zeabur.md>)

### AI overview

Zeabur says an attacker used a never-rotated cluster admin token and other exposed credentials to reach its platform database and read 3,218,965 customer environment-variable records. The report traces the breach through plaintext, long-lived credentials, broad permissions, shared infrastructure and undetected use of valid access. It recommends inventorying and rotating credentials, limiting each key's reach, separating customer workloads and backups from core systems, and alerting on bulk secret reads and unusual admin activity. For stored secrets, it describes envelope encryption with customer-specific key boundaries and decryption at point of use; keeping an encryption key beside the data defeats encryption. WorkOS Vault is presented as one implementation, with BYOK support, but its API key can still authorize decryption and must be protected. Projects moved to customer-controlled servers were outside the database read's scope.

### Source excerpt

A cluster admin token created in 2024 and never rotated led to 3.2 million customer environment variables being read. What that means if your product stores credentials for your customers.

## For Coding Agents, the Repository Matters

DevFeed: [For Coding Agents, the Repository Matters](<https://devfeed.tech/articles/for-coding-agents-the-repository-matters-93687.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2606.28235>)

Author: Daniel Russo

Published: 2026-10-21T04:00:00Z

Content type: article

Language: en

Sources: [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [AI-assisted coding](<https://devfeed.tech/topics/ai-assisted-coding.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [Repository](<https://devfeed.tech/topics/repository.md>)

Tags: [coding-agents](<https://devfeed.tech/tags/coding-agents.md>), [cs-ai](<https://devfeed.tech/tags/cs-ai.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [evaluation](<https://devfeed.tech/tags/evaluation.md>), [oversight](<https://devfeed.tech/tags/oversight.md>), [pull-request](<https://devfeed.tech/tags/pull-request.md>), [repository](<https://devfeed.tech/tags/repository.md>), [software](<https://devfeed.tech/tags/software.md>)

### AI overview

In this comparison of agent and human pull requests across public GitHub repositories, repository context accounts for a larger share of resolution-time differences for agents. Multilevel models found that, across 280 repositories, between-repository variance was 1.76 times higher for agent pull requests (95% CI 1.41-2.18). For waits of several hours, a repository one standard deviation slower than average was associated with typical waits about 2.8 times longer for agents and 2.2 times longer for humans. Rejection showed a similar pattern, while differences in review rounds and comments were not detectable. A proxy for the initiating developer explained little of the gap; stated agent policies were too rare to assess. The findings support treating the receiving repository, alongside the agent, as a unit for evaluating and overseeing coding agents.

### Source excerpt

arXiv:2606.28235v2 Announce Type: replace Abstract: In July 2026, about 1,200 AI agents in an internal OpenAI evaluation, meant to run in isolation, used a shared package server as a message board, and about 700 of them joined an attack on Hugging Face. An automated scorer judged each agent on its own task, and the attack was coordinated through infrastructure the agents shared. Coding agents meet shared infrastructure every day, in the software repositories that receive their pull requests. Yet field studies still judge coding agents by outcomes pooled across repositories, such as merge rates and merge times. We asked how much these outcomes depend on the receiving repository, and whether they depend on it more than human contributions do. Using multilevel models, we compared agent pull requests from the AIDev dataset of public GitHub repositories with human pull requests in the same repositories. About two-fifths of the variation in how long agent pull requests take to be resolved lies between repositories, after accounting for the pull request, the agent, and the repository's observable attributes. In 280 repositories, with covariates common to both groups, the between-repository variance is 1.76 times as large for agent as for human pull requests (95% CI 1.41 to 2.18). For waits of several hours, a repository one standard deviation slower than average multiplies the typical wait by about 2.8 for agent and 2.2 for human pull requests. Rejection shows the same pattern, while for review rounds and comments the difference is not detectable. A proxy for the role of the developer who started the agent accounts for little of the difference, and stated agent policies were too rare to test. These results suggest that the oversight and evaluation of coding agents need the repository, and not only the agent, as a unit.

## Email notifications for repository push events have been retired

DevFeed: [Email notifications for repository push events have been retired](<https://devfeed.tech/articles/email-notifications-for-repository-push-events-have-been-retired-87803.md>)

Original publisher: [Read original article](<https://github.blog/changelog/2026-10-15-email-notifications-for-repository-push-events-have-been-retired>)

Author: Allison

Published: 2026-10-15T13:42:19Z

Content type: release

Language: en

Sources: [GitHub Changelog](<https://devfeed.tech/sources/github-changelog.md>)

Topics: [Push Notifications](<https://devfeed.tech/topics/push-notifications.md>), [email](<https://devfeed.tech/topics/email.md>), [Repository](<https://devfeed.tech/topics/repository.md>), [Continuous integration](<https://devfeed.tech/topics/continuous-integration.md>)

Tags: [community-engagement](<https://devfeed.tech/tags/community-engagement.md>), [email](<https://devfeed.tech/tags/email.md>), [github-actions](<https://devfeed.tech/tags/github-actions.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [notifications](<https://devfeed.tech/tags/notifications.md>), [repository](<https://devfeed.tech/tags/repository.md>), [retired](<https://devfeed.tech/tags/retired.md>), [smtp](<https://devfeed.tech/tags/smtp.md>)

### AI overview

GitHub retired email notifications for repository push events on October 15, 2026, to reduce spam and abuse. The post recommends using a GitHub Actions workflow triggered by push events to send email through your own SMTP server or email provider.

### Source excerpt

As of October 15, 2026, email notifications for repository push events have been retired and are no longer sent. We shut down this feature to help prevent spam and abuse.... The post Email notifications for repository push events have been retired appeared first on The GitHub Blog.

## Triage role users or higher can now archive pull requests

DevFeed: [Triage role users or higher can now archive pull requests](<https://devfeed.tech/articles/triage-role-users-or-higher-can-now-archive-pull-requests-77567.md>)

Original publisher: [Read original article](<https://github.blog/changelog/2026-10-08-triage-role-users-or-higher-can-now-archive-pull-requests>)

Author: Allison

Published: 2026-10-08T19:01:42Z

Content type: release

Language: en

Sources: [GitHub Changelog](<https://devfeed.tech/sources/github-changelog.md>)

Topics: [identity and access management](<https://devfeed.tech/topics/identity-and-access-management.md>), [Repository](<https://devfeed.tech/topics/repository.md>)

Tags: [archive](<https://devfeed.tech/tags/archive.md>), [collaboration-tools](<https://devfeed.tech/tags/collaboration-tools.md>), [improvement](<https://devfeed.tech/tags/improvement.md>), [pull-requests](<https://devfeed.tech/tags/pull-requests.md>), [triage](<https://devfeed.tech/tags/triage.md>)

### AI overview

Repository users with the triage, write, maintain, or admin role can now archive and unarchive pull requests; previously, only admins could archive them. Archiving automatically closes a pull request and blocks new comments, reactions, and automated comments, making its conversation read-only. Archived pull requests are hidden from public view but remain visible to those four repository roles. Unarchiving restores commenting and reactions but does not reopen the pull request.

### Source excerpt

Users with the triage role or higher in a repository can now archive and unarchive pull requests. Previously, archiving was limited to repository administrators, requiring trusted triagers to hand routine... The post Triage role users or higher can now archive pull requests appeared first on The GitHub Blog.

## CVE-2026-85706: Critical GitLab Path Traversal Is Being Exploited

DevFeed: [CVE-2026-85706: Critical GitLab Path Traversal Is Being Exploited](<https://devfeed.tech/articles/gitlab-vulnerability-under-active-exploitation-enables-unauthenticated-data-exfiltration-64465.md>)

Original publisher: [Read original article](<https://www.infoq.com/news/2026/10/gitlab-critical-vulnerabilities/>)

Author: Sergio De Simone

Published: 2026-10-03T16:00:00Z

Content type: news

Language: en

Sources: [InfoQ](<https://devfeed.tech/sources/infoq.md>)

Topics: [GitLab](<https://devfeed.tech/topics/gitlab.md>), [Exploit](<https://devfeed.tech/topics/exploit.md>), [known exploitable vulnerabilities](<https://devfeed.tech/topics/known-exploitable-vulnerabilities.md>), [gitlab-ci](<https://devfeed.tech/topics/gitlab-ci.md>), [Repository](<https://devfeed.tech/topics/repository.md>)

Tags: [active-exploitation](<https://devfeed.tech/tags/active-exploitation.md>), [addition](<https://devfeed.tech/tags/addition.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [continuous-deployment](<https://devfeed.tech/tags/continuous-deployment.md>), [continuous-integration](<https://devfeed.tech/tags/continuous-integration.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [cybersecurity](<https://devfeed.tech/tags/cybersecurity.md>), [development](<https://devfeed.tech/tags/development.md>), [devops](<https://devfeed.tech/tags/devops.md>), [exploited](<https://devfeed.tech/tags/exploited.md>), [gitlab](<https://devfeed.tech/tags/gitlab.md>), [gitlab-critical-vulnerabilities](<https://devfeed.tech/tags/gitlab-critical-vulnerabilities.md>), [gitlab-vulnerability](<https://devfeed.tech/tags/gitlab-vulnerability.md>), [kev](<https://devfeed.tech/tags/kev.md>), [kev-catalog](<https://devfeed.tech/tags/kev-catalog.md>), [news](<https://devfeed.tech/tags/news.md>), [patch](<https://devfeed.tech/tags/patch.md>), [path-traversal](<https://devfeed.tech/tags/path-traversal.md>), [security-vulnerabilities](<https://devfeed.tech/tags/security-vulnerabilities.md>), [software-supply-chain](<https://devfeed.tech/tags/software-supply-chain.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>)

### AI overview

A critical path-traversal flaw in self-managed GitLab CE/EE can let unauthenticated remote attackers read arbitrary files when an instance has at least one public project. The article reports confirmed exploitation, describes potential exposure of secrets and CI/CD credentials, and recommends patching, reviewing logs, and rotating affected credentials.

### Source excerpt

CVE-2026-85706 is a critical GitLab path-traversal vulnerability that has moved beyond theoretical risk into confirmed exploitation. It affects self-managed GitLab CE/EE and could allow an unauthenticated remote attacker to read arbitrary files from the GitLab. By Sergio De Simone

## Accessibility statements highlighted on repository overview

DevFeed: [Accessibility statements highlighted on repository overview](<https://devfeed.tech/articles/accessibility-statements-highlighted-on-repository-overview-71389.md>)

Original publisher: [Read original article](<https://github.blog/changelog/2026-10-01-accessibility-statements-highlighted-on-repository-overview>)

Author: Allison

Published: 2026-10-01T19:04:32Z

Content type: release

Language: en

Sources: [GitHub Changelog](<https://devfeed.tech/sources/github-changelog.md>)

Topics: [Web Accessibility (a11y)](<https://devfeed.tech/topics/web-accessibility.md>), [GitHub](<https://devfeed.tech/topics/github.md>), [Repository](<https://devfeed.tech/topics/repository.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [github](<https://devfeed.tech/tags/github.md>), [overview](<https://devfeed.tech/tags/overview.md>), [repository](<https://devfeed.tech/tags/repository.md>)

### AI overview

GitHub repository overviews now highlight an `ACCESSIBILITY.md` file placed in the repository root, `.github/`, or `docs/`. For public repositories, an accessibility statement can also be added or proposed from the Community Standards page. The improvement is available on all GitHub plans at github.com and is scheduled for GitHub Enterprise Server 3.24.

### Source excerpt

You can now find an ACCESSIBILITY.md file in your repository's root, the .github/ directory, or the docs/ directory highlighted on the repository overview. You can also add or propose an...

## Repository custom runner settings for Dependabot

DevFeed: [Repository custom runner settings for Dependabot](<https://devfeed.tech/articles/repository-custom-runner-settings-for-dependabot-71401.md>)

Original publisher: [Read original article](<https://github.blog/changelog/2026-09-29-repository-custom-runner-settings-for-dependabot>)

Author: Allison

Published: 2026-09-29T19:10:00Z

Content type: release

Language: en

Sources: [GitHub Changelog](<https://devfeed.tech/sources/github-changelog.md>)

Topics: [Dependabot](<https://devfeed.tech/topics/dependabot.md>), [Repository](<https://devfeed.tech/topics/repository.md>)

Tags: [administrator](<https://devfeed.tech/tags/administrator.md>), [advanced-security](<https://devfeed.tech/tags/advanced-security.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [configure](<https://devfeed.tech/tags/configure.md>), [dependabot](<https://devfeed.tech/tags/dependabot.md>), [dependency-scanning](<https://devfeed.tech/tags/dependency-scanning.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [environment](<https://devfeed.tech/tags/environment.md>), [github](<https://devfeed.tech/tags/github.md>), [github-enterprise-server](<https://devfeed.tech/tags/github-enterprise-server.md>), [github-hosted-runners](<https://devfeed.tech/tags/github-hosted-runners.md>), [optional](<https://devfeed.tech/tags/optional.md>), [repository](<https://devfeed.tech/tags/repository.md>), [runner](<https://devfeed.tech/tags/runner.md>), [security](<https://devfeed.tech/tags/security.md>), [security-updates](<https://devfeed.tech/tags/security-updates.md>), [settings](<https://devfeed.tech/tags/settings.md>), [type](<https://devfeed.tech/tags/type.md>), [updates](<https://devfeed.tech/tags/updates.md>), [version](<https://devfeed.tech/tags/version.md>)

### AI overview

Repository administrators can configure where Dependabot version and security update jobs run, extending runner settings previously available at the organization level. For private and internal repositories on github.com, choose a labeled runner and optionally set a custom label and runner group; without a custom label, Dependabot uses `dependabot`. Labeled runners can be self-hosted or larger GitHub-hosted runners. Alternatively, choose the standard GitHub-hosted runner. These controls are hidden for public repositories and on GitHub Enterprise Server, and security configurations do not currently enforce the settings. Configure them in repository Settings under Advanced Security -> Dependency scanning -> Dependabot version updates.

### Source excerpt

As a repository administrator, you can now configure the runner type, optional custom label, and optional runner group for Dependabot version and security updates. This extends the runner configuration already...

## The @Find Annotation in Hibernate

DevFeed: [The @Find Annotation in Hibernate](<https://devfeed.tech/articles/the-find-annotation-in-hibernate-60329.md>)

Original publisher: [Read original article](<https://www.baeldung.com/java-hibernate-find-annotation>)

Author: Graham Cox

Published: 2026-09-26T04:20:54Z

Content type: tutorial

Language: en

Sources: [Baeldung](<https://devfeed.tech/sources/baeldung.md>)

Topics: [Hibernate](<https://devfeed.tech/topics/hibernate.md>), [Repository](<https://devfeed.tech/topics/repository.md>), [Java](<https://devfeed.tech/topics/java.md>), [jpa](<https://devfeed.tech/topics/jpa.md>), [annotation-processor](<https://devfeed.tech/topics/annotation-processor.md>), [Database](<https://devfeed.tech/topics/database.md>), [Maven](<https://devfeed.tech/topics/maven.md>), [implementation](<https://devfeed.tech/topics/implementation.md>)

Tags: [database](<https://devfeed.tech/tags/database.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [hibernate](<https://devfeed.tech/tags/hibernate.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [implementation](<https://devfeed.tech/tags/implementation.md>), [java](<https://devfeed.tech/tags/java.md>), [jpa](<https://devfeed.tech/tags/jpa.md>), [jpa-hibernate](<https://devfeed.tech/tags/jpa-hibernate.md>), [maven](<https://devfeed.tech/tags/maven.md>), [repository](<https://devfeed.tech/tags/repository.md>)

### AI overview

This tutorial explains how to use Hibernate's @Find annotation with method query naming conventions. It covers Hibernate setup, Jakarta Data dependencies, compile-time repository generation, database entities, repository interfaces, and dependency injection.

### Source excerpt

Learn about how to use the @Find annotation in Hibernate to generate a repository implementation using method query naming conventions. The post The @Find Annotation in Hibernate first appeared on Baeldung.

[Next page](<https://devfeed.tech/topics/repository.md?cursor=WyIyMDI2LTA5LTI2VDA0OjIwOjU0KzAwOjAwIiwgImNkZTU3ZDQxLTU4MDEtNDc1NS04N2M1LWM0Y2M0NGMzNjgyZCJd>)