fix(deps): replace taffydb
with @jsdoc/salty
#117
Merged
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.
The
taffydb
package has issues. It's unclear what license it uses, and it has an alleged "security vulnerability" that's completely bogus but nonetheless causesnpm audit
to squawk. See https://github.com/jsdoc/jsdoc/blob/main/packages/jsdoc-salty/README.md for details about both issues.This PR replaces
taffydb
with@jsdoc/salty
, a drop-in replacement fortaffydb
that's licensed under the Apache License 2.0. It has no known security issues, bogus or otherwise.To test this PR, I generated docs for JSDoc 4.x using this template:
Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly: