Skip to content

Redact secret-like source literals in output - #23

Draft
YoungJinJung wants to merge 1 commit into
mainfrom
issue-18-redact-literals
Draft

Redact secret-like source literals in output#23
YoungJinJung wants to merge 1 commit into
mainfrom
issue-18-redact-literals

Conversation

@YoungJinJung

Copy link
Copy Markdown
Contributor

Summary

  • Redact secret-like source literals before materializing folder names or graph labels.
  • Cover source defaults, conditions, return/value expressions, and annotation/decorator arguments.
  • Add a regression test that verifies generated folders and index.html do not contain a secret literal.

Closes #18.

Validation

  • npm test
  • node --check quarkify.mjs

@YoungJinJung

Copy link
Copy Markdown
Contributor Author

Cross-platform note: #27 adds the Windows/macOS/Linux CI matrix that should validate this change across supported operating systems before release.

Quarkify now replaces secret-like literals with a stable redacted label before materializing folder names or graph data, reducing the chance that generated output becomes a second copy of credentials found in source.

Constraint: Keep structural topology visible while hiding sensitive literal values by default.
Rejected: Remove all literal labels | too much loss of useful non-sensitive structure for local analysis.
Confidence: medium
Scope-risk: moderate
Directive: Treat generated output as shareable metadata only after literal redaction has run.
Tested: npm test; node --check quarkify.mjs
Related: #18
@YoungJinJung
YoungJinJung force-pushed the issue-18-redact-literals branch from 4865c47 to 5b5fcbf Compare June 16, 2026 07:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Redact source literals before writing generated folders and HTML

1 participant