Skip to content

docs: add npx ECOMPROMISED recovery steps#1319

Closed
stablegenius49 wants to merge 1 commit intoruvnet:mainfrom
stablegenius49:pr-factory/issue-1231-ecompromised-troubleshooting
Closed

docs: add npx ECOMPROMISED recovery steps#1319
stablegenius49 wants to merge 1 commit intoruvnet:mainfrom
stablegenius49:pr-factory/issue-1231-ecompromised-troubleshooting

Conversation

@stablegenius49
Copy link
Copy Markdown
Contributor

Summary\n- add a troubleshooting entry for npm ECOMPROMISED / Lock compromised failures during npx installs\n- document safe recovery steps: cache clean/verify first, then integrity-index-only reset if needed\n- include retry commands for both ruflo and claude-flow packages\n\n## Validation\n- git diff --check\n- attempted markdown lint, but README has many pre-existing lint violations unrelated to this change\n\nCloses #1231

Copy link
Copy Markdown

@xkonjin xkonjin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Quick review pass:

  • This looks docs-only from the diff, so I don’t see a code-path blocker here.
  • Please still verify the examples/commands in README.md against current behavior so we don’t merge stale instructions.
  • If there’s a linked feature change behind this, CI should include at least one smoke check that matches the documented flow.

Copy link
Copy Markdown
Owner

ruvnet commented Mar 17, 2026

Closing — the ECOMPROMISED error is an npm cache issue that's better documented in npm's own troubleshooting. Adding npm-specific recovery steps to our README would go stale quickly. Users can find the fix via npm cache clean --force. Thanks for flagging this!

@ruvnet ruvnet closed this Mar 17, 2026
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.

3 participants