-
Notifications
You must be signed in to change notification settings - Fork 43
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
Expose internals as library for programmatic use #212
Comments
I am planning on supporting this. I think it's going to be possible with my refactor in #226. As a result, the package will also have types! |
@quinnturner Thanks for the response! I now see that the PR is merged, but I don’t see updates to the documentation. Is this still open? Or should I dive into the code and I’d see exports for the key audit functions? |
I was probably a bit hasty to say it was supported 😅 I'd like it to be though, and it's not too far off. Short todo list for me to make this supported:
I will try to release something this week that adds all of that! |
Hey, I haven't forgotten about this. I've had to spend all my extra time on another professional project which will be done within the week. I will try to tackle this afterwards. Thanks for understanding! |
Support added with this PR #271. I mostly just exported some functions that I thought would be useful. I expect the API will change based on feedback from the community. I haven't written documentation for it yet either, but the bare bones are there including pretty solid TypeScript types. |
At @getoslash, we use a handmade script (https://gist.github.com/paambaati/b7dd99d67f5402b62d7f8ef95ef65e01) to auto-generate yarn resolutions for audit-vi vulnerabilities.
It would be massively useful if the package also exposed some of its internals as an API, so we could avoid shelling to the command itself and instead use
audit-CI
as a library.The text was updated successfully, but these errors were encountered: