Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create a "collect_manifest" scan option to generate a lockfile when none exists #3772

Closed
DennisClark opened this issue May 9, 2024 · 1 comment

Comments

@DennisClark
Copy link
Member

DennisClark commented May 9, 2024

Proposed: a new "collect_manifest" scan option that prompts scancode to figure out the dependencies when there is no clearly specified manifest, and then store that generated lockfile in the scan results.

Benefits:

  • Better dependency results
  • Traceability of the dependency results by making the generated manifest persistent
@pombredanne pombredanne changed the title Create a "collect_manifest" scan option to generate a manifest when none exists Create a "collect_manifest" scan option to generate a lockfile when none exists Jun 3, 2024
@pombredanne
Copy link
Member

After consideration, we would rather not have a scancode option for this. Instead it will be a separate standalone executable that is tracked in https://github.com/nexB/dependency-inspector/ and specifically in this issue:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants