docs(pt-br): update README_PT-BR.md to reflect current project description and features - #7405
Conversation
…ption and features
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (7)
WalkthroughThis PR rewrites and restructures multiple localized README files: new header/hero and TOC, expanded CLI help blocks, updated scanning examples and cloud/dashboard notes, refreshed templates/community/bounties text, contributor avatar grids, and normalized license footers. ChangesMultilingual README Updates
Estimated code review effort: Possibly related issues:
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (2)
README_PT-BR.md (2)
309-309: ⚡ Quick winTerminology consistency: "template" in honeypot threshold description.
This line uses "IDs de template distintos" which mixes Portuguese with the English term "template". For consistency with line 50 which uses "modelos", consider using "IDs de modelo distintos" instead.
Suggested terminology alignment
- -hpt, -honeypot-threshold int número de IDs de template distintos necessários para sinalizar um host como honeypot (padrão 15) + -hpt, -honeypot-threshold int número de IDs de modelo distintos necessários para sinalizar um host como honeypot (padrão 15)🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@README_PT-BR.md` at line 309, Update the Portuguese wording for the honeypot threshold flag (-hpt, -honeypot-threshold) to use consistent terminology: replace "IDs de template distintos" with "IDs de modelo distintos" so the flag description matches the term "modelos" used elsewhere (e.g., line 50); ensure the rest of the text and the default "(padrão 15)" remain unchanged.
42-42: ⚡ Quick winInconsistent terminology: "templates" vs "modelos".
Line 42 uses "templates de vulnerabilidade" while line 50 uses "modelos de vulnerabilidades" to refer to the same concept. For consistency and clarity, consider using the same term throughout this section.
The static analysis tool suggests that "templates" is a foreign term and "modelos" is preferred in Portuguese.
Suggested terminology alignment
-- Formato YAML simples para criar e customizar templates de vulnerabilidade +- Formato YAML simples para criar e customizar modelos de vulnerabilidadeAlso applies to: 50-50
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@README_PT-BR.md` at line 42, The text uses inconsistent terminology ("templates de vulnerabilidade" vs "modelos de vulnerabilidades"); standardize to the preferred Portuguese term "modelos" throughout the document—e.g., replace "templates de vulnerabilidade" and "templates" occurrences with "modelos de vulnerabilidade" (or "modelos de vulnerabilidades" if you prefer plural consistency) and ensure the phrase at line 42 and the one at line 50 match exactly; scan the README_PT-BR.md for any other uses of "template(s)" and update them to the chosen "modelo(s)" form so the section uses a single consistent term.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@README_PT-BR.md`:
- Line 50: In the README_PT-BR.md line containing the sentence "Temos um
[repositório dedicado](https://github.com/projectdiscovery/nuclei-templates) que
abriga vários tipos de modelos de vulnerabilidades, contribuídos por
**milhares** de pesquisadores e engenheiros de segurança.", replace the
inaccurate "milhares" count with the actual contributor number (e.g., "366") or
a correct range like "300+" so the text reflects the real contributor count;
update the bolded token and any similar nearby occurrences to keep wording
consistent.
---
Nitpick comments:
In `@README_PT-BR.md`:
- Line 309: Update the Portuguese wording for the honeypot threshold flag (-hpt,
-honeypot-threshold) to use consistent terminology: replace "IDs de template
distintos" with "IDs de modelo distintos" so the flag description matches the
term "modelos" used elsewhere (e.g., line 50); ensure the rest of the text and
the default "(padrão 15)" remain unchanged.
- Line 42: The text uses inconsistent terminology ("templates de
vulnerabilidade" vs "modelos de vulnerabilidades"); standardize to the preferred
Portuguese term "modelos" throughout the document—e.g., replace "templates de
vulnerabilidade" and "templates" occurrences with "modelos de vulnerabilidade"
(or "modelos de vulnerabilidades" if you prefer plural consistency) and ensure
the phrase at line 42 and the one at line 50 match exactly; scan the
README_PT-BR.md for any other uses of "template(s)" and update them to the
chosen "modelo(s)" form so the section uses a single consistent term.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
| - Suporte a múltiplos protocolos: TCP, DNS, HTTP, SSL, WHOIS, JavaScript, Code e mais | ||
| - Integração com Jira, Splunk, GitHub, Elastic e GitLab | ||
|
|
||
| Temos um [repositório dedicado](https://github.com/projectdiscovery/nuclei-templates) que abriga vários tipos de modelos de vulnerabilidades, contribuídos por **milhares** de pesquisadores e engenheiros de segurança. |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Description: Verify the contributor count for nuclei-templates repository
# Fetch contributor count from GitHub API
echo "Fetching contributor count for nuclei-templates..."
gh api repos/projectdiscovery/nuclei-templates/contributors --paginate --jq 'length' | awk '{s+=$1} END {print "Total contributors:", s}'
# Also check the English README for comparison
echo -e "\nChecking English README for reference..."
rg -n "researchers.*engineers" README.mdRepository: projectdiscovery/nuclei
Length of output: 184
Update contributor count to reflect actual data.
The nuclei-templates repository has 366 contributors, not thousands. The change from "300+" to "milhares" (thousands) is inaccurate and should be corrected or reverted.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@README_PT-BR.md` at line 50, In the README_PT-BR.md line containing the
sentence "Temos um [repositório
dedicado](https://github.com/projectdiscovery/nuclei-templates) que abriga
vários tipos de modelos de vulnerabilidades, contribuídos por **milhares** de
pesquisadores e engenheiros de segurança.", replace the inaccurate "milhares"
count with the actual contributor number (e.g., "366") or a correct range like
"300+" so the text reflects the real contributor count; update the bolded token
and any similar nearby occurrences to keep wording consistent.
|
@coderabbitai create an issue for this PR about errors in docs |
|
Tip For best results, initiate chat on the files or code changes. 🧩 Analysis chain
I'll share the link to the created issue once the script runs. 🏁 Script executed: Length of output: 55
It tracks the following errors found in
|
Summary by CodeRabbit