osendowment / osendowment/model
Create a tool to identify dependencies for manifest-less ecosystems
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 20
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Ecosystems like JavaScript or Python use one of multiple different kinds of manifests to specify dependencies — package.json, deno.json, requirements.txt, pyproject.toml.
But some ecosystems don't use manifests, like C and C++. And even when there are quasi-manifests, like CMakeLists.txt, these are very difficult to parse.
How can we create tools to identify dependency graphs for manifest-less ecosystems?
Contributor guide
No contributing guide indexed for this repository
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 discusses dependency discovery for package.json, deno.json, requirements.txt, pyproject.toml, and CMakeLists.txt, with C and C++ as manifest-less examples. Start by comparing the existing manifest approaches and defining which ecosystems and dependency sources the tool should support. Done requires an agreed approach for identifying dependency graphs in the selected cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, cmake, cpp, javascript, python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100