BUG: invalid number of commits reported
Open
Nobody has claimed this yet.
kind/bug
- Dominant language
- Go
- Stars
- 5.7k
- Forks
- 723
- Avg merge
- 19h 30m
- Merged PRs (30d)
- 1
Description
Running scorecard on https://github.com/danielaparker/jsoncons/commits/master reports
"Info: all commits (3) are checked with a SAST tool
Thera are a lot more commits in the repo, though. I would have expected Scorecard to look at 30 commits (at least that's how it used to work)
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
Reproduce the report by running Scorecard against the jsoncons repository and observing why only 3 commits are checked. Read the commit-counting and SAST-checking paths to compare the current behavior with the expected 30-commit limit. Done means the check reports the intended number of commits and relevant tests cover the regression.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- devtools, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100