search

aboutcode-org / scancode-toolkit

:mag: ScanCode detects licenses, copyrights, dependencies by "scanning code" ... to discover and inventory open source and third-party packages used in your code. Sponsored by NLnet project https://nlnet.nl/project/vulnerabilitydatabase, the Google Summer of Code, Azure credits, nexB and others generous sponsors!
https://aboutcode.org/scancode/
2.15k stars 553 forks source link

Add support for buildpack.toml manifest #3477

Open pombredanne opened 1 year ago

pombredanne commented 1 year ago

This is a package manifest format for Heroku and Packeto: See https://github.com/search?q=path%3A**%2Fbuildpack.toml&type=code&ref=advsearch

Adding support would consist in:

  1. Research and document here as comment the buildpack format specification and various spec versions
  2. Collect a few representative test files and attach as comment keeping track of the URL provenance for each
  3. Create a new packagedcode/buildpack.py module with an overall structure similar to that of existing modules. Implement parsing and creating a Package.
  4. Add tests in a new test_buildpack.py test module using the collect test files
  5. Add extra unit tests for single functions
hp77-creator commented 11 months ago

Hey @pombredanne , Looks good issue, I would like to learn more about it and maybe contribute to it, Shall I work on it If there's no one else working on the same?

arshad-muhammad commented 1 month ago

@pombredanne I'm interested in extending the project to handle the buildpack.toml manifest and wanted to check in to ensure I understand the full scope of the task.

Could you please provide a bit more context regarding: The specific parts of the project that need this support? Any particular edge cases or functionality you'd like to be considered? How you envision the buildpack.toml information being utilized in the system (e.g., dependency handling, build steps)?