modusensus/dsh-mneme - Open Source PR Review Scorecard

🧠 The memory that dreams — cross-session memory for DeepSeek Harness. Offline & private, auto-consolidates in its sleep (autoDream), visualized in a memory panel.

C-Rank Grade: S (Elite) - 75/100

External PR Merge Rate: 93%

Response Time: 1d

First Timer Success: 100%

Frequently Asked Questions

Is modusensus/dsh-mneme welcoming to first-time open-source contributors?

modusensus/dsh-mneme has a recorded first-timer success rate of 100.0%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.

How fast can I expect code review feedback on my pull request?

Maintainers in modusensus/dsh-mneme respond to incoming external pull requests in approximately 30.9 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 74.9 C-Rank™ score (S Tier) represent?

The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 74.9 places modusensus/dsh-mneme in the S tier.

What is the external contributor pull request merge rate for modusensus/dsh-mneme?

The external contributor pull request merge rate for modusensus/dsh-mneme is 93.3%, based on public PR activity from non-core contributors.

Are there Good First Issues available in modusensus/dsh-mneme?

modusensus/dsh-mneme does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.

modusensus
modusensus/dsh-mnemeS•Elite112
GitHub
Back to Explorer
modusensus

modusensus/dsh-mneme

112
Active (30d)S•Elite(75/100)JavaScript

🧠 The memory that dreams — cross-session memory for DeepSeek Harness. Offline & private, auto-consolidates in its sleep (autoDream), visualized in a memory panel.

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Empathetic Technical Mentor

Warmth Score
7.5/10
Patience Score
8.2/10
Nitpick Rate
20%

Collaborative maintainer environment in modusensus/dsh-mneme. Reviews community pull requests with focus on project quality.

What Contributors Actually Say

Discussions in modusensus/dsh-mneme focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.

Hidden Friction Signals

Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.

Unwritten Rules

  • •1) Keep PR scope strictly aligned with the linked issue.
  • •2) Ensure local linters pass before opening a review.
  • •3) Maintain full test coverage for modified logic.

Top PR Submission Do's

  • •Ensure code complies with the project coding style
  • •Keep PRs scoped to a single concern
  • •Include context and link to the related issue

Top PR Friction Pitfalls (Don'ts)

  • •Do not submit PRs without linking an issue
  • •Do not break existing tests without fixing them
  • •Do not mix unrelated refactors in a single PR
Response Velocity
1 days+
Standard maintainer review cycle

Average Response Latency

Tracks hours until a maintainer leaves a review, comment, or PR response.

Merge Efficiency
93.3%
High acceptance rate for external PRs

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
100.0%
Strong first-timer PR acceptance rate

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
5 core
Small core review team
Diagnostic Health HUD
93.3%
Merge Gauge
100.0%
1st-Timer
Community Vibe74/100

Embed C-Rank Badge

Show contributors that your repository actively reviews and merges external pull requests.

GetMerged C-Rank badge for modusensus/dsh-mneme
[![GetMerged C-Rank](https://getmerged.abhishekco.de/api/badge/modusensus/dsh-mneme)](https://getmerged.abhishekco.de/modusensus/dsh-mneme?utm_source=github&utm_medium=badge)

Active Good First Issues (5)

View on GitHub

背景 #164 的论文调研(六篇)给 A1/C1/C2 提供了理论锚点,其中遗忘三篇(2604.00131 / 2601.18642 / 2604.02280)共同指向同一件事:记忆系统需要一层「受访问频率与时间调制的热度衰减」,否则要么无限膨胀(长程性能 0.45→0.05 的反面教材),要么一刀切硬删(丢掉本可复活的低频高价值记忆)。 本 issue 立项 D 批次:heat 热度衰减,按刻意保守的路径落地:opt-in → 真实数据 → 对照论文找偏差。 理论依据(三篇) Oblivion(2604.00131,EMNLP 2026):遗忘 = 降低可及性而非删除——经验随时间变得不易获取,但可被强化或情境线索重新激活;且「帮过忙的记忆应被强化」。与本项目 archived/forgotten 两列的既有设计同构,本 issue 是它的量化延伸。 FadeMem(2601.18642):不同记忆应有不同衰减率,由语义相关性、访问频率、时间模式三者调制;存储可缩减 45%。幂

📅 Opened Sep 17, 2026💬 3 comments
Quality: 90/100Contribute

动机 社区讨论里有一条值得正面回应的批评:记忆插件的存储容易退化成"记事本"——写进去容易,被实际复用很难,且用户看不见复用情况。这条批评在 dsh-mneme 里恰好是可量化的:recall 回执(recordRecall,检索场景已落库)、llm_audit_logs、dream_runs 三处数据都在。缺的不是数据,是把"记忆被用了没有"变成用户与维护者都看得见的信号。 三个用途: 用户侧:第一次能看见"我的记忆被用上了吗",而不是对着列表猜; 调参侧:僵尸记忆率是巩固/归档策略的直接依据(哪些该降权、哪些该进巩固候选); 产品侧:为后续 heat(热度升权)与图谱(结构化关联)提供基线数据——复用率改善与否,要有 before/after 才说得清。 形态建议(v1) 数据面:一个只读聚合路由(如 GET /api/dsh-mneme/recall-stats?window=30d): 近 N 天被召回 / 被注入的 Top-N 记忆(含次

📅 Opened Sep 17, 2026💬 1 comment
Quality: 90/100Contribute

背景 #175 定论:宿主 minimal 预设(极简模式)按设计压制全部 runtime context——记忆注入 / 用户画像 / hot memory 在极简模式会话中一律不送达模型,且行为对用户不可见。README 已补「已知边界」文档,但文档是被动的;面板应主动提示。 方案 注入回调 / 面板读会话头 agentPreset 检测到 minimal 且 autoInject 开启时,状态页 / 设置页明确标注:「注入按宿主 minimal 预设设计关闭」+ 解法链接(standard 模式 / agent-presets.default: standard / AGENTS.md 过渡) 注意 --dump-config 显示 bundle 默认值、不反映用户层 settings.yaml 覆盖——判断实际生效值只能读会话头,不要走 dump-config 验收 minimal 会话:面板显示明确提示与解法,不再是静默黑盒 standard 会话:无提示(零打扰) 难度:低,适合新手。与「注入可观测性」issue 有交集(第 2 点重叠),实现时可合并认领。

📅 Opened Sep 15, 2026💬 0 comments
Quality: 90/100Contribute

背景 #175 的定论暴露了一个产品面缺口:用户完全看不见「此刻注入了什么」——注入内容、入选理由、体积,全都不透明。极端案例:宿主 minimal 预设按设计压制全部 runtime context,注入静默失效,用户只能靠逐帧解压会话日志才能定位(见 #175)。 方案 注入预览视图(设置页或状态页新增):展示当前会话「如果此刻组装 prompt,会注入什么」—— 注入块构成:hot memory 段 + 跨会话记忆条目(标题/重要性/入选理由:语义命中 or 规则命中) 体积(字符数/约 token) 当前开关状态(autoInject / threshold / maxItems) preset=minimal 标注:读会话头 agentPreset,检测到 minimal 且 autoInject 开启时,明确标注「注入按宿主 minimal 预设设计关闭(详见 README 已知边界)+ 解法」,不再静默 备注 第 2 点也可独立实现(见同批「极简模式状态提示」issue),两者实现时

📅 Opened Sep 15, 2026💬 0 comments
Quality: 90/100Contribute

背景 对面板前端做了第一遍 WCAG 导向审计。骨架及格:按钮/输入框基本都有 aria-label、装饰图标统一 aria-hidden、星级评分有 role="img"+数值标签、会话列表用 tree/treeitem 语义、大弹层有 role="region"+aria-label+Esc 关闭、开关控件有 aria-checked/aria-expanded。 系统性缺口(按 WCAG 四原则): 缺口 位置 原则 状态变化无播报 保存成功/失败、队列刷新、resolve 完成——纯视觉 span,无 aria-live 可感知 操作缺上下文 冲突队列「保留 A」读屏只听到「保留 A」,不知是哪一对 可理解 状态卡无语义 「最近巩固/待确认冲突」是纯 div,不可聚焦、无 heading 层级 可操作 弹层焦点管理 记忆库 sheet 开时不移焦、无 focus trap、关闭不还焦 可操作 图表无替代 ego 关系图 SVG 无可访问名称与数据摘要 可感知 对比度未审计 三级灰字 11px 在浅色主题下疑似低于 4.5:1 可感知

📅 Opened Sep 15, 2026💬 0 comments
Quality: 90/100Contribute
Looking for more JavaScript beginner tasks?Explore JavaScript GFI

Contributor Community Vibe Feedback

Rate what actually matters after opening a pull request here.

Have you contributed to this repo?

Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.

3 ratings required
Maintainer helpfulness
Review speed
Beginner friendliness

Contributor Compatibility & Review Speed Analysis for modusensus/dsh-mneme

When evaluating whether to contribute to modusensus/dsh-mneme, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.

Currently, maintainers of modusensus/dsh-mneme acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 93.3% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to modusensus/dsh-mneme

01

Is modusensus/dsh-mneme welcoming to first-time open-source contributors?

modusensus/dsh-mneme has a recorded first-timer success rate of 100.0%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.

02

How fast can I expect code review feedback on my pull request?

The initial maintainer response time averages ~1 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 74.9 C-Rank™ score represent?

The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 74.9 places modusensus/dsh-mneme in the Elite tier.

04

What is the external contributor pull request merge rate for modusensus/dsh-mneme?

The external pull request merge rate is 93.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.

05

Are there beginner Good First Issues open in modusensus/dsh-mneme?

modusensus/dsh-mneme does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for modusensus/dsh-mneme are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.