feat: granular check-related information in reports#177
Merged
randomicecube merged 2 commits intomainfrom Jun 2, 2025
Merged
Conversation
Relates to Report feedback #166
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Relates to #166
Example of the current state of the report below
Software Supply Chain Report of ericcornelissen/shescape - 3304b1744c0691dbc71f063708023f5d364a7988
📚 Table of Contents
Enabled Checks
The following checks were requested project-wide:
source_codesource_code_shadeprecatedforksprovenancecode_signaturealiased_packagesIgnore Configuration Summary
Ignored Checks Per Dependency 🔧
These dependencies had specific checks excluded based on the configuration file.
Note: If
allis listed, every check is ignored for that dependency.@types/.+source_code_shaconcat-map@0.0.1source_code,source_code_sha,forksfile-entry-cache@8.0.0source_code,source_code_sha,forksmicro-spelling-correcter@1.1.1allSummary of Findings
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: 1071
❗ Packages with no source code URL (⚠️ ⚠️ ⚠️ ): 5
⛔ Packages with repo URL that is 404 (⚠️ ⚠️ ⚠️ ): 1
🔧 Packages with inaccessible commit SHA/tag (⚠️ ⚠️ ): 28
🔒 Packages without code signature (⚠️ ⚠️ ): 0
🔓 Packages with invalid code signature (⚠️ ⚠️ ): 0
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(6)
[][][][][][]List of packages with available source code repos but with inaccessible commit SHAs/tags(28)
[][][][][][][]['rollup@4.41.0'][][][][][][][][][][][][][][][][][][][]['tap-parser@17.0.0']All packages have code signature.
All packages have valid code signature.
Call to Action:
👻What do I do now?
For packages without source code & accessible SHA/release tags:
For packages without code signature:
For packages with invalid code signature:
Notes
Other info:
Source code repo is not hosted on GitHub: 3
This could be due, for example, to the package being hosted on a different platform.
This does not mean that the source code URL is invalid.
However, for non-GitHub repositories, not all checks can currently be performed.
['brace-expansion@1.1.11'][][]Glossary
source_code: Whether a repo URL is present and validsource_code_sha: Whether a commit SHA is available and validforks: Whether the repo is a forkdeprecated: Whether the package is marked deprecatedprovenance: Whether build provenance/attestation is providedcode_signature: Whether a code signature is present and validaliased_packages: Whether a package is aliased under a different nameReport created by dirty-waters.
Report created on 2025-06-01 18:19:25