clearlydefined / clearlydefined/service

Highlight what triggered NOASSERTION

Open
#656 6 comments 1 reaction 0 assignees View on GitHub
enhancement
Dominant language
TypeScript
Stars
51
Forks
46
PR merge metrics
No merged PRs in 30d

Description

For files within a component that are marked as NOASSERTION, highlight in the file what the tooling thinks may be license info. Otherwise, I am scanning some really long files trying to find why the tooling thought maybe there was license info on that file.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.