Abusive warning about cybersecurity for routine code reviews
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What issue are you seeing?
Hello,
Paid customer here.
Using it for OSS projects, php, libgd (used by php and countless projects), and dependencies used along other projects.
I took a sub to do exactly this task, automate code review, add tests, etc.
It was working well until a few days ago. Now almost every single code review ends with:
This content can't be shown
We take extra caution with cybersecurity requests. If you’re a security professional, you may be able to apply for Trusted Access.
Trusted Access: https://chatgpt.com/cyber/
Learn more: https://help.openai.com/en/articles/20001326
even when no issue found but somehow it sees it as a "hack attempt".
I own the code, public codes for most or about to be released.
And that cyber page request does not work, I filled three times, it says success, nothing then. Going back to it says to try again. You may consider using actual working services instead.
Also if that cannot be fixed, refund will be requested as it breaks my primary usage :(.
What steps can reproduce the bug?
Any code review related to memory usage or similar, in my case I use C/C++.
What is the expected behavior?
No response
Additional information
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No repository file, test, or entry point is identified. Start by reproducing a code review involving memory usage in C/C++ and compare reviews that are blocked with those that are not; a complete fix would let routine reviews finish without the cybersecurity warning and make the Trusted Access flow behave consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, cpp, php, rust
- Domain
- devtools, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100