Rename this library? (and if so, alternative names wanted!)
- Dominant language
- Go
- Stars
- 63
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
Originally I called this `osv-detector` because I felt "auditor" and "scanner" were a bit overloaded, and I was considering if this was to be published as a package somewhere, `osv-detector` would be less likely to have already been taken.
However, I'm now thinking if it would be better to call it something else for a few reasons:
1. ~I'm thinking about additional checks we could be doing, like #75~ (I don't think this is probably worth it)
2. Go packages/binaries are not restricted to unique names, and `osv-detector` might not be as easy to find as say "security-auditor"
3. `osv-detector` is sort of wrong, as this tool isn't for "detecting OSVs"...
But the real blocker for me is what to actually call it instead - I'd prefer to not use "lockfile" (e.g `lockfile-auditor`) because that'd put us back in the same place if we start auditing more than them (but then maybe it's fine?)
Contributor guide
Assessment
This issue has not been assessed yet.