aboutcode-org / aboutcode-org/dependency-inspector

dependency-inspector OR deplock

Open
#32 0 comments 0 reactions 2 assignees Claimed by @pombredanne View on GitHub
Dominant language
Go
Stars
2
Forks
3
PR merge metrics
No merged PRs in 30d

Description

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.?

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.