Clarify C# and Kotlin detection versus analysis support
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 82/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Domain
- documentation
Research direction
Start by reading the COMING_SOON status for C# and Kotlin in backend/app/scanners/language_support.py, then the detection signals in backend/app/scanners/classification.py. Next, open docs/languages.md and find where the supported ecosystem list is described. Done when the guide says that detecting C# (.csproj, .sln) and Kotlin (.kt, build.gradle.kts) does not mean dependency analysis exists, with no change to the list and no release date.
Written by the indexing model from the issue text.
Description
Summary
C# and Kotlin can be detected from repository signals, but their language support status is currently COMING_SOON. The supported ecosystem list should make this distinction clear so detection is not mistaken for dependency analysis support.
Affected files
backend/app/scanners/language_support.pybackend/app/scanners/classification.pydocs/languages.md
Scope
Make this a documentation-only contribution. Add a clear section describing the current detection signals and the fact that dependency analysis is not implemented for these languages. Do not change the supported ecosystem list or imply a release date.
Acceptance criteria
docs/languages.mdexplains that C# and Kotlin detection does not mean dependency analysis is implemented.- The documentation identifies relevant signals, including
.csproj,.sln,.kt, andbuild.gradle.kts. - The existing supported ecosystem list remains unchanged.
- No release date or timeline is promised.
- The wording matches the current
COMING_SOONstatus inlanguage_support.pyand detection logic inclassification.py.
Testing expectations
No application tests are required for this documentation-only change. Review the updated language guide against the referenced classification and support-status code.
- Dominant language
- Python
- Stars
- 2
- Forks
- 1
- Avg merge
- 1h 22m
- Merged PRs (30d)
- 2
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from ayushdoesdev/verspect
-
enhancement good first issue
Difficulty 3/5 1-2 days Newbie friendliness 62/100
ayushdoesdev/verspect#4 ·
-
enhancement good first issue
Difficulty 3/5 1-2 days Newbie friendliness 62/100
ayushdoesdev/verspect#3 ·
-
enhancement good first issue
Difficulty 3/5 1-2 days Newbie friendliness 62/100
ayushdoesdev/verspect#2 ·
All issues in ayushdoesdev/verspect
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
pytest-dev/pyfakefs#1367 · 1 comment ·
Maintainers usually reply within 2 days
-
IFEvalG exclude_word_harder misses the keyword next to punctuation, at the start or end of the text, and in other letter casePossibly taken @damienen claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
allenai/open-instruct#2151 ·
Maintainers usually reply within 1 day
-
feat(plan): support convertorLabels and convertorAffinity in Plan resourcePossibly taken @AmenB claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
RedHatQE/openshift-python-wrapper#2849 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 25 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
libnativeapi/nativeapi#21 ·