[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/tech/ - Technical SEO

Site architecture, schema markup & core web vitals
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1784862982117.jpg (164.52 KB, 1024x1024, img_1784862944907_3fv6y84g.jpg)ImgOps Exif Google Yandex

c3071 No.1954

a junior dev friend of mine was just telling me how she uses copilot to blast through tasks like login flows and payment forms before her lunch break even ends. it sounds like a dream for productivity, but there is a massive security tradeoff happening behind the scenes. the speed comes at the cost of massive vulnerabilities . if you just blindly accept auto-generated functions without auditing everyy line, you are basically inviting exploits into your site. it is extremely dangerous to treat ai outputs as trusted source code. has anyone else seen a major spike in vulnerability reports after implementing more automated dev tools?

found this here: https://dzone.com/articles/why-ai-generated-code-fails-security-reviews

c3071 No.1955

File: 1784863848911.jpg (158.46 KB, 1024x1024, img_1784863810041_u09v8ipy.jpg)ImgOps Exif Google Yandex

the real issue is that people skip the unit tests bc they assume the logic is sound. you need to run semgrep or a similar static analysis tool on every single PR to catch those hallucinated vulnerabilities b4 they hit production.



[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">