LoRexxar/Kunlun-M

【PR征集】公开征集PR

Closed

#158 opened on Jul 22, 2021

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Python (301 forks)batch import
help wanted

Repository metrics

Stars
 (2,038 stars)
PR merge metrics
 (Avg merge 1m) (11 merged PRs in 30d)

Description

经过长时间的深思熟虑，我必须承认我没有能力完美维护KunLun-M项目，毕竟现在仍然是个人维护。

于是决定将部分我已经确认没精力做的部分公开出来，如果有幸能够在社区得到PR，将会对KunLun-M的完善前进一大步。如果感兴趣，可以联系我。

  • 完善完整的开发、使用文档

KunLun-M目前为止所有的文档都集中在Readme.md以及/docs中。 在Cobra-W之后我就没精力维护开发文档了。其中非常多我更新的功能我都没办法在文档中体现出来。

要求： 1、使用Markdown格式完成。 2、使用文档、开发文档可以分两个阶段完成。

  • 靠谱的开源的组件安全扫描解决方案

在2.5.0版本当中，我增加了以项目为单位的组件数据表。 image 要求是在这个数据基础上找到一个能在开源基础上完成的组件安全扫描方案。

要求: 1、在/core/vendors.py的基础上开发。 2、开源项目承受不起巨大的爬虫数据量，需要找到一个能够达成的解决方案，效果差一点儿也能接受。

  • 其他待补充

如果有朋友有意愿为KunLun-M更新新功能，也可以留言沟通。

Contributor guide

Research direction
For documentation, review the existing documentation in the Readme.md and /docs directory to identify gaps and outdated content. For the component security scanning, examine the `/core/vendors.py` file to understand the current data schema, then research open source vulnerability databases like NVD or GitHub Advisory that can be integrated without excessive crawling. The maintainer invites discussion, so consider leaving a comment to clarify scope before starting.
Tech stack
python
Domain
securitydocumentation
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
MarkdownPythonbasic understanding of static analysis
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40