Skip to content

Conversation

@jssblck
Copy link
Contributor

@jssblck jssblck commented Jun 27, 2025

Overview

Cortez and I are working with a customer that would benefit from having our internal rendergraph tool being public; this PR adds it to the FOSSA CLI repository and releases.

rendergraph itself is sort of a "best effort" tool so it doesn't have tests; I don't think it's worth adding to docs as we would expect users to basically use this when we suggest it for troubleshooting.

Acceptance criteria

rendergraph is available in FOSSA CLI releases.

Testing plan

Sadly, just manual testing

Risks

Yet more random stuff plugged into FOSSA CLI releases 🙃

Metrics

None

References

None

Checklist

  • I added tests for this PR's change (or explained in the PR description why tests don't make sense).
  • If this PR introduced a user-visible change, I added documentation into docs/.
  • If this PR added docs, I added links as appropriate to the user manual's ToC in docs/README.ms and gave consideration to how discoverable or not my documentation is.
  • If this change is externally visible, I updated Changelog.md. If this PR did not mark a release, I added my changes into an ## Unreleased section at the top.
  • If I made changes to .fossa.yml or fossa-deps.{json.yml}, I updated docs/references/files/*.schema.json AND I have updated example files used by fossa init command. You may also need to update these if you have added/removed new dependency type (e.g. pip) or analysis target type (e.g. poetry).
  • If I made changes to a subcommand's options, I updated docs/references/subcommands/<subcommand>.md.

@jssblck jssblck requested a review from a team as a code owner June 27, 2025 17:20
@jssblck jssblck requested a review from csasarak June 27, 2025 17:20
Comment on lines 8 to 13
# Installation from source

0. Install `rust`: https://www.rust-lang.org/tools/install
1. Clone this repo locally
2. Run `cargo install --path rendergraph` from the parent directory.
3. Use as `fossa analyze -o | rendergraph` (you can also `cat output.json | rendergraph`- any stdin works)
Copy link
Contributor

@csasarak csasarak Jun 27, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[nit] Recommend moving this down to the bottom of the readme. A customer who wants to use this can just download the binary, so the docs about how to use it are way more important than how to build it IMO.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point, moved

A list of things I've thought of to add. Have an idea? Add it to this list via PR!

- [ ] Account for graph pruning (use source units to do this)
- [ ] Support graphviz output
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IMO, this really ought to be a part of Ficus. Being able to just instruct the CLI to do this is a better user-experience than "please download this bin from GH."

This PR is totally fine, I'm just saying we should have that as future work item in this list IMO.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good idea, updated

@jssblck jssblck merged commit abbef28 into master Jun 27, 2025
19 checks passed
@jssblck jssblck deleted the rendergraph branch June 27, 2025 21:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants