0xwilliamortiz/humanizer-cli

Undisclosed telemetry violates data sovereignty promises and creates immediate enterprise compliance risk given evidence of beaconing in launch.mjs.

Cost Zero architectural change required but requires removing or opt-in'ing the existing beaconing code to align marketing with reality.

Decoupling detection patterns from binary compilation enables rapid response to evolving AI writing styles without forcing heavy npm dependency bumps for users.

Cost Requires refactoring C source to parse external configuration and adding validation logic in Node launcher.

Reduces infrastructure costs and latency significantly but creates an accuracy ceiling that may limit adoption against sophisticated AI-generated text later.

Cost Low immediate implementation cost but high technical debt requiring future migration path planning when rules become insufficient.

Allows leveraging the massive npm ecosystem for distribution while maintaining performance, yet complicates CI/CD pipelines with multi-OS native builds and security scanning hurdles at 10x scale.

Cost High maintenance overhead requiring distinct build jobs per platform/architecture to manage binary signing and vulnerability scans across environments.

Prevents catastrophic churn and legal exposure by resolving the critical contradiction between README promises of zero data leakage and existing launcher beaconing code detected in launch.mjs.

Cost Low engineering effort to disable or disclose, but high immediate reputational risk if discovered during user auditing.

Enables rapid adaptation to evolving AI writing patterns without forcing full binary rebuilds and npm version bumps for every minor detection tweak.

Cost Medium architectural shift requiring validation logic in the C runtime or Node wrapper to safely parse external rule files.

Ensures seamless installation experience for non-technical users via npm without requiring them to manually manage zip contents or system paths.

Cost Low complexity addition to existing launcher logic but necessary maintenance burden in CI/CD pipelines for Windows artifacts.

Reinforces the core differentiator of instant, zero-dependency execution that appeals to users avoiding cloud subscriptions and GPU requirements.

Cost Low maintenance overhead though requires periodic heuristic tuning against new AI model outputs to maintain accuracy.

Expands the product scope from a simple detector/editor into a guardrail system, allowing users to safely leverage cloud LLMs without compromising text confidentiality.

Cost Medium UI/UX development needed to shift CLI workflow towards interactive prompt generation and external tool integration guidance.

Discrepancy between launch.mjs telemetry and README offline guarantees creates immediate legal liability and erodes user trust upon audit

Cost Low technical change but high communication risk to retract marketing promises or remove tracking code

Decoupling detection rules from C binary compilation accelerates iteration cycles and reduces CI/CD friction for heuristic changes

Cost Moderate refactor required to externalize parsing logic currently embedded in compiled source files

Dynamic extraction reduces installer complexity but introduces silent failure vectors during runtime initialization that lack test coverage

Cost Low engineering effort since mechanism exists, requires improved error handling monitoring in CI pipelines

sources/launch.mjs confirms telemetry contradicting README offline guarantee creating immediate compliance and trust failures requiring audit

Cost Modify launcher to remove or gate telemetry endpoints and update documentation regarding data handling transparency immediately

On-demand extraction of executables from zips allows supply chain injection where malicious binaries replace legitimate ones without integrity checks

Cost Implement cryptographic signature verification and content hashing for all archived assets before execution in the launcher logic

Relying on external binaries distributed through package managers lacks build provenance transparency hindering vulnerability analysis and patch verification

Cost Publish reproducible builds with SBOMs and cryptographic signatures pinned in the node script download validation logic

README guarantees no data leaves the machine but launch.mjs implements anonymized usage beaconing

Cost High - requires legal/marketing alignment and code refactor to remove or disclose telemetry

launch.mjs explicitly handles zip extraction for .exe ensuring cross-platform npm install works without manual user steps

Cost Medium - increases startup complexity and file structure management in postinstall scripts

Aligns with core capability of 33 Wikipedia rules implemented in C binary without external runtime dependencies

Cost Low - leverages existing codebase architecture for offline processing

package.json and launch.mjs confirm hybrid distribution model enabling global install while isolating core logic

Cost Medium - requires maintaining native builds for each OS alongside the JS wrapper