Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

fix(skill): ownership check graded must when sibling checks are out of view

未关闭
#12 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
68/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
活跃
技术栈
javascript
领域
devtools, security

调研方向

Start by reading SKILL.md and security.md, then inspect the dotnet eval fixture and expected.md mentioned in the issue. Update the access-control guidance so findings without visible ownership evidence go under Questions, and run the dotnet eval three consecutive times. Done when those runs pass and the dotnet-webhook and nestjs findings retain their previous grades.

由索引模型根据 Issue 内容生成。

描述

bug eval

What

On the dotnet fixture the review grades a missing ownership check (IDOR) on a new endpoint as must, while expected.md asks for a question unless sibling endpoints visibly check ownership.

Why

It is the one false positive in the v0.2.0 eval runs. A must on an assumption about unseen code breaks the "proof or it's dropped" rule.

Acceptance criteria

  • SKILL.md and security.md say that an access-control finding needs either a visible sibling that checks ownership or a visible data model that ties the resource to the caller; otherwise it goes under Questions.
  • The dotnet eval reports it under Questions in three consecutive runs.
  • The dotnet-webhook and nestjs access-control findings stay graded as before.
主要语言
JavaScript
星标
0
派生
0
PR 合并指标
30 天内没有已合并 PR

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

devmaxxx/stackwise 的其他 Issue

查看 devmaxxx/stackwise 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。