microsoft / microsoft/component-detection
Add composer.json as source for component detection
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 553
- Forks
- 135
- Avg merge
- 20h 58m
- Merged PRs (30d)
- 6
Description
I initially created the issue here https://github.com/microsoft/sbom-tool/issues/478, but it seemed to be the wrong repo.
Composer is a dependency manager for PHP: https://getcomposer.org/
It would be cool to also create an SBOM out of composer.json files. That's why I ask you to add composer.json as a source for component detection. I would also be happy to help if needed.
Thanks,
Juergen
AB#2140410
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by locating the repository's existing package-manager detection entry points and compare their behavior with Composer's dependency metadata; done means composer.json files produce the expected SBOM components, with coverage through the repository's existing test path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- devtools, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100