aboutcode-org / aboutcode-org/dependency-inspector

dependency-inspector OR deplock

Abierto
#32 0 comentarios 0 reacciones 2 asignados Reclamado por @pombredanne Ver en GitHub
Lenguaje dominante
Go
Estrellas
2
Forks
3
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

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

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.