Comfy-Org / Comfy-Org/ComfyUI-Manager

Is there any reason some custom node still cannot be installed until the security level is lowered? Even if it's a kijai one?

Open
#2,233 3 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
16.1k
Forks
2.5k
Avg merge
5d 4h
Merged PRs (30d)
13

Description

Image

Is it due to:
- the custom node uses some admin level libraries or something
- the custom node updates some risky libraries
- the custom node has not been registered properly to comfyui manager and was not monitored or something?

I am asking to avoid installing any custom node in the future and to know precisely why, in this case it is from kijai which known so there should not be any problem and I can bypass the security thing by insalling through git clone I suppose. But still why the message?

Contributor guide

No contributing guide indexed for this repository

Research direction

The issue names no file, test, or entry point. Reproduce the custom-node installation at different security levels, then trace the warning to determine whether it relates to library permissions, risky dependency updates, or node registration. Done means documenting the cause and the safe installation conditions.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
security, tooling
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.