Skip to content

feat: implement full CyberPot Attack Map redesign #4

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
khulnasoft-bot wants to merge 2 commits into
base: master
Choose a base branch
from
Open

feat: implement full CyberPot Attack Map redesign #4

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d6ea26d
feat: implement full CyberPot Attack Map redesign
Feb 6, 2026
b4ddfc9
Update static/realtime-animations.js
khulnasoft-bot Aug 24, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions .vscode/settings.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
{
"files.readonlyInclude": {
"**/*": true
}
}
Comment on lines +1 to +5

@coderabbitai coderabbitai Bot Feb 6, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🔴 Critical

Do not commit workspace settings that mark all files as read-only.

This setting will prevent any developer from editing files in VSCode after cloning the repo. It appears to be a leftover from the code-generation/preview environment (v0.app). Remove this file or at least remove the "**/*": true glob.

🤖 Prompt for AI Agents 
In @.vscode/settings.json around lines 1 - 5, Remove the workspace setting that
makes every file read-only in .vscode/settings.json by deleting the "\"**/*\":
true" entry (or remove the entire .vscode/settings.json file) so developers can
edit files after cloning; ensure no other read-only-wide globs remain in that
file and commit the cleaned settings (or remove the file) instead.

Loading