[GH-ISSUE #2615] How to resolve NodeVersionStatusFlagged ? My latest version updates to my custom node are not showing up in the ComfyUI Manager and I don't know why it's being marked as NodeVersionStatusFlagged. #1001

New issue

Open

opened 2026-10-27 21:24:54 +00:00 by bsakaguchi · 1 comment

bsakaguchi commented

2026-10-27 21:24:54 +00:00

Owner

Originally created by @JasonHoku on GitHub (Feb 15, 2026).
Original GitHub issue: https://github.com/Comfy-Org/ComfyUI-Manager/issues/2615

It took me a bunch of digging to discover why my new custom node version weren't showing up in the manager.

I had to look through the manager source code to find it calls https://api.comfy.org/nodes/{your-node-id-here}/versions?statuses=NodeVersionStatusActive

And then I removed ?statuses=NodeVersionStatusActive to see that my node status is NodeVersionStatusFlagged.

I didn't get any warning or message or reason and now users are confused about how to access the latest updated.

How do we find info on how to resolve this? I've been searching and trying fixes for hours.

Originally created by @JasonHoku on GitHub (Feb 15, 2026). Original GitHub issue: https://github.com/Comfy-Org/ComfyUI-Manager/issues/2615 It took me a bunch of digging to discover why my new custom node version weren't showing up in the manager. I had to look through the manager source code to find it calls https://api.comfy.org/nodes/{your-node-id-here}/versions?statuses=NodeVersionStatusActive And then I removed ?statuses=NodeVersionStatusActive to see that my node status is NodeVersionStatusFlagged. I didn't get any warning or message or reason and now users are confused about how to access the latest updated. How do we find info on how to resolve this? I've been searching and trying fixes for hours.

bsakaguchi commented

2026-10-27 21:24:55 +00:00

Author

Owner

@JasonHoku commented on GitHub (Feb 20, 2026):

Update:

So basically if your versions are getting marked as NodeVersionStatusFlagged it's been queued for manual review by the ComfyUI Security Review Council. In my limited experience, they get around to these within a few days.

The only place I've found that you can find additional info on why the version is flagged is in the Comfy Org official Discord server in the #security-review-council channel. I went there to ask some questions and they were very helpful, prompt and friendly. Please note that this is a free and public service so be concise and patient, allow at least a week before requesting a manual review, users should still be able to access your latest updates by using the latest or nightly channels of your node. Also note that personally, for me I was NOT able to see reasons or posts on my most recent versions that were flagged for review for some reason (I could only find one entry in that channel from over a month ago) but they still approved my versions after a few days of them being flagged after they got caught up. Thank you Comfy Org Security Review Council!

I would like to mark this issue as closed since I now understand the reason for versions not showing up being the NodeVersionStatusFlagged status and it meaning they're awaiting manual review, however it would be nice for us developers to be alerted that it's been marked as flagged, the reason for the flag, and that it's awaiting manual review. I've seen a few people asking the same question so I think it would help.

For The ComfyUI Manager Team (Possible Security Issue?):

During my research of this issue I also found that people were still able to download my flagged custom node if they used the latest or nightly versions. Also if the security scan hadn't finished and it was still marked as NodeVersionStatusPending the version WOULD show up in ComfyUI Manager, it would only disappear after the security scan finished and marked it as flagged. It seems like it sort of defeats the purpose of using NodeVersionStatusActive and the security scans if people can still download them through the manager. Perhaps a shield icon 🛡 next to versions that have been scanned and passed or approved could inform people of this?

Thank you again, all OSS dev's and helpers.

@JasonHoku commented on GitHub (Feb 20, 2026): Update: So basically if your versions are getting marked as `NodeVersionStatusFlagged` it's been queued for manual review by the ComfyUI Security Review Council. In my limited experience, they get around to these within a few days. The only place I've found that you can find additional info on why the version is flagged is in the Comfy Org official Discord server in the `#security-review-council` channel. I went there to ask some questions and they were very helpful, prompt and friendly. Please note that this is a free and public service so be concise and patient, allow at least a week before requesting a manual review, users should still be able to access your latest updates by using the `latest` or `nightly` channels of your node. Also note that personally, for me I was NOT able to see reasons or posts on my most recent versions that were flagged for review for some reason (I could only find one entry in that channel from over a month ago) but they still approved my versions after a few days of them being flagged after they got caught up. Thank you Comfy Org Security Review Council! I would like to mark this issue as closed since I now understand the reason for versions not showing up being the `NodeVersionStatusFlagged` status and it meaning they're awaiting manual review, however it would be nice for us developers to be alerted that it's been marked as flagged, the reason for the flag, and that it's awaiting manual review. I've seen a few people asking the same question so I think it would help. ## For The ComfyUI Manager Team (Possible Security Issue?): During my research of this issue I also found that **people were still able to download my flagged custom node if they used the latest or nightly versions**. Also **if the security scan hadn't finished and it was still marked as NodeVersionStatusPending the version WOULD show up in ComfyUI Manager**, it would only disappear after the security scan finished and marked it as flagged. It seems like it sort of defeats the purpose of using `NodeVersionStatusActive` and the security scans if people can still download them through the manager. Perhaps a shield icon 🛡 next to versions that have been scanned and passed or approved could inform people of this? Thank you again, all OSS dev's and helpers.

bsakaguchi referenced this issue

2026-10-27 21:33:24 +00:00

[PR #1001] [MERGED] Add ObjectFusion custom nodes #1644