Problem Description
I have a Debian machine, but most of my dev tooling is handled via a mix of Nix/HomeManager, mise, venvs or nix-direnv type setups. This means that all machine guard sees on my machine is the Debian packages, everything else is effectively hidden. This includes it not seeing my chrome install (with multiple data dirs/profiles) since it comes from HM (which might be more of a bug than the rest of this).
Proposed Solution
I don't expect dev guard to support all the weird us cases me or other users might have, but if there was a way to supplement the data with our own findings, and have it also work nicely with the step security dashboards then we could fix coverage holes ourselves if they are important enough to us.
Alternatives Considered
Build direct support for everything, which also works of course. But I think an extension point is more future proof, and then you can always upstream the ones that make sense.
Additional Context
No response
Problem Description
I have a Debian machine, but most of my dev tooling is handled via a mix of Nix/HomeManager, mise, venvs or nix-direnv type setups. This means that all machine guard sees on my machine is the Debian packages, everything else is effectively hidden. This includes it not seeing my chrome install (with multiple data dirs/profiles) since it comes from HM (which might be more of a bug than the rest of this).
Proposed Solution
I don't expect dev guard to support all the weird us cases me or other users might have, but if there was a way to supplement the data with our own findings, and have it also work nicely with the step security dashboards then we could fix coverage holes ourselves if they are important enough to us.
Alternatives Considered
Build direct support for everything, which also works of course. But I think an extension point is more future proof, and then you can always upstream the ones that make sense.
Additional Context
No response