pkg:maven/com.simplaex/java-druid-client@1.2.0 got UNKNOWN for mcn_scm_authenticity_1, expect FAILED
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 210
- Forks
- 36
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 2
Description
Reproduce the issue
I ran this on Macaron at commit 9d5de67040be5975ebfd211f34b8d11f4de567b2
# Assume the development environment has been setup
macaron analyze -purl pkg:maven/com.simplaex/java-druid-client@1.2.0
The issue
Macaron discovered the git repository for this PURL at https://github.com/simplaex/dummies. This is different from the expected git repository at https://github.com/simplaex/java-druid-client.
However, this is not Macaron fault as https://github.com/simplaex/dummies is defined in https://repo1.maven.org/maven2/com/simplaex/java-druid-client/1.2.0/java-druid-client-1.2.0.pom.
In additions, I was expecting mcn_scm_authenticity_1 check to failed instead of UNKNOWN.
2025-03-25 11:43:56,350 [macaron.slsa_analyzer.checks.base_check:run:95] [INFO] ----------------------------------
2025-03-25 11:43:56,350 [macaron.slsa_analyzer.checks.base_check:run:96] [INFO] BEGIN CHECK: mcn_scm_authenticity_1
2025-03-25 11:43:56,350 [macaron.slsa_analyzer.checks.base_check:run:97] [INFO] ----------------------------------
2025-03-25 11:43:56,350 [macaron.slsa_analyzer.checks.base_check:run:111] [INFO] Check mcn_scm_authenticity_1 run UNKNOWN on target pkg:maven/com.simplaex/java-druid-client@1.2.0.
2025-03-25 11:43:56,350 [macaron.slsa_analyzer.checks.base_check:run:117] [DEBUG] Check result: [(<Confidence.HIGH: 1.0>, ['Not Available.'])]
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
Run macaron analyze -purl pkg:maven/com.simplaex/java-druid-client@1.2.0 at commit 9d5de67040be5975ebfd211f34b8d11f4de567b2 and inspect the mcn_scm_authenticity_1 check result. Compare the repository in the Maven POM with the expected repository and make the check report FAILED rather than UNKNOWN when they differ.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, python
- Domain
- build-system, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100