feat: add strength reports and safe exports - #11
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Closes #7.
Rebuilds the strength-report/export work on top of the current
mainafter the older PR became non-mergeable.Changes
--reportfor readable strength reports on stderr while preserving stdout for CLI scripting.--format jsonwith schema metadata, entropy, strength, warnings, recommendations, and enabled-set coverage data.--redactfor shareable JSON metadata.--output,--quiet, and--forcefor safer local exports with extension checks, overwrite protection, parent-directory handling, and owner-only file permissions where supported.main, including strict option validation, positional preset validation, recovery hints, and enabled-set coverage guarantees.docs/STRENGTH_REPORTS.md.yargsto the Node 18-compatible^17.7.2line.Current verification
48b634add0bb89b9bb54e175fbca45501fabae1e.28635014960: the failing assertion expected bare--lengthto fail, but the pinned yargs behavior treated it as absent. The smoke test now avoids that version-sensitive missing-value assertion while retaining invalid numeric length, coverage, unknown option, mode, output, JSON, redaction, quiet, and help coverage.28635912132:SECURITY.mdnow includes the required "Do not paste generated passwords into GitHub issues" guidance while preserving broader secret-handling warnings.28636621882succeeded across Node 18, Node 20, and Node 22.mergeable: true.Notes