-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: add dirty waters #317
base: main
Are you sure you want to change the base?
Conversation
Hey Aman, I've tinkered with it a bit on a fork and it's working now (see https://github.com/randomicecube/sbom.exe/actions/runs/13355966510/job/37298751984) |
@algomaster99 working! Fails because of 4 cases where no source code repo was found, but it's working! |
Thanks @randomicecube !
great out of sight out of mind :D
Pasting here for convenience
I tried to Ctrl + F on the output of Also, a feature-request: It would be nice to know which maven module these dependencies belong to. |
@algomaster99 I believe some of them come from
This one does not return the table's third entry, however (at least not with version 0.0.4, just 0.0.7). Interesting to note too that I think this allowed me to catch a bug on the |
If you mean this chains-project/dirty-waters#67, I think I sent you an e-mail regarding this, I'll bump it |
Oh so these were plugins. Now it makes sense!
Any idea where that is coming from? Yes. The coordinates have 4 items - |
I already dealt with the packaging, I just didn't know about classifiers (which I think is what |
@LogFlames it seems that there is feature request to add JSON support for |
I think |
@randomicecube so it seems you have fixed the issue with the 4th unknown dependency? What was the problem? Also, I tried to manually find the 3 packages that don't have source URLs and I could find 2ish out of 3.
|
^ignoring cache for this run; need to remove that param from the workflow before merging |
Software Supply Chain Report of chains-project/sbom.exe - HEADEnabled ChecksThe following checks were specifically requested:
How to read the results 📖Dirty-waters has analyzed your project dependencies and found different categories for each of them:
Total packages in the supply chain: 287❗ Packages with no source code URL ( ⛔ Packages with repo URL that is 404 ( 🔧 Packages with inaccessible commit SHA/tag ( 🔒 Packages without code signature ( :unlocked: Packages with invalid code signature ( Fine grained information🐬 For further information about software supply chain smells in your project, take a look at the following tables. Source code links that could not be found(10)
List of packages with available source code repos but with inaccessible commit SHAs/tags(32)
The package manager (maven) does not support checking for deprecated packages. List of packages without code signature(41)
All packages have valid code signature. The package manager (maven) does not support checking for provenance. The package manager (maven) does not support checking for aliased packages. Call to Action:👻What do I do now?For packages without source code & accessible SHA/release tags:
For deprecated packages:
For packages without code signature:
For packages with invalid code signature:
For packages without provenance:
For packages that are aliased:
NotesOther info:
Report created by dirty-waters. Report created on 2025-03-21 10:29:56
|
@randomicecube just noticed the report! Thanks! I will take a look at this later this week ;) |
No description provided.