aboutcode-org / aboutcode-org/dependency-inspector

dependency-inspector OR deplock

未關閉
#32 0 則留言 0 個 reaction 已指派 2 人 已被 @pombredanne 認領 在 GitHub 檢視
主要語言
Go
星號
2
分支
3
PR 合併指標
30 天內沒有已合併 PR

描述

This project is named dependency-inspector but the README is for DepLock with no mention of dependency-inspector. I think I can understand DepLock as a tool under dependency-inspector but there is no indication that we are working on anything other than DepLock. Most other inspectors are tools to analyze dependencies from a manifest file, not tools to create "missing" manifest files.

The question is:

- Should the repo be renamed deplock? OR
- Should we update the README to explain how DepLock fits into some broader roadmap for dependency-inspector.?

貢獻指南

這個儲存庫沒有索引到貢獻指南

評估

這個 Issue 還沒有評估資料。

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。