Repository navigation
chore(deps): upgrade Rails 7.2 -> 8.1.4 - #51
Merged
Merged
Conversation
…ipts - scripts/28_prostaff_audit.sh: bridge that runs ProStaff-Audit against the local API and maps findings.json to FINDING: lines consumed by 15_full_audit.sh; graceful skip when deps/API unavailable - scripts/15_full_audit.sh: register 28 as non-destructive, slow (skip in --quick mode) - front/check-waf-fingerprint.sh: detect Cloudflare/Vercel JS challenge blocking before running curl-based scripts against production - front/check-security-headers-live.sh: same 22 security header checks via Chromium/Playwright headless, bypasses the WAF challenge - tools/playwright/: capture.js + capture-cors.js + package.json for Playwright-based header capture - BURP-SEED.md: full walkthrough for seeding Burp with live traffic - README.md: add script rows, WAF/Playwright note, reports table entry
Rails 7.2 reached EOL on 2026-08-09; Brakeman EOLRails check was failing CI with High confidence since 2026-10-12. - Gemfile: rails ~> 8.1.4 (was ~> 7.2.3 >= 7.2.3.1) - annotate replaced with annotaterb 4.25.0 — annotate 3.2.0 declares activerecord < 8.0 and is incompatible with Rails 8.x; annotaterb is the maintained fork with Rails 8 support - Gemfile.lock: updated (rails 8.1.4, annotaterb 4.25.0, rswag 2.17.0, rspec-rails 8.0.4, factory_bot_rails 6.5.1) - README.md + .pentest/README.md: version badges and stack references updated to Rails 8.1
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 21484269 | Triggered | Generic Password | 5eeba71 | .pentest/scripts/28_prostaff_audit.sh | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secret safely. Learn here the best practices.
- Revoke and rotate this secret.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
Contributor
📦 Dependency Security Check✅ No known vulnerabilities found. View Report |
Up to standards ✅🟢 Issues
|
| Metric | Results |
|---|---|
| Complexity | 0 |
NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.
Contributor
🔒 Brakeman Security Scan
✅ No high confidence issues found. |
Contributor
🔍 Semgrep Static Analysis
|
Contributor
🔐 Security Scan SummaryStatic Analysis (SAST)
Dynamic Analysis (DAST)
✅ All security checks passed! |
Contributor
CodeQL Analysis
Ver alertas completos no Security tab. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
EOLRailsHIGH confidence estava quebrando o CI (Security Scanrun 38291311139) desde 2026-10-12annotate 3.2.0substituído porannotaterb 4.25.0— declaraactiverecord < 8.0, incompatível com Rails 8.x;annotaterbé o fork mantido com suporte a Rails 8rswag 2.17.0,rspec-rails 8.0.4,factory_bot_rails 6.5.1atualizados como efeito colateralTest plan
EOLRailsHIGH resolvido)bundle exec rails --version→Rails 8.1.4bundle exec rspec)docker compose up -d && curl localhost:3333/health