Skip to content

Persian translation, originally from #3227#3370

Open
tghosth wants to merge 95 commits into
v5.0.0from
v5.0.0_fa
Open

Persian translation, originally from #3227#3370
tghosth wants to merge 95 commits into
v5.0.0from
v5.0.0_fa

Conversation

@tghosth

@tghosth tghosth commented Jul 16, 2026

Copy link
Copy Markdown
Collaborator

This Pull Request relates to persian translation

Original PR was #3227

tghosth and others added 30 commits June 1, 2025 15:37
* translations in progress

* Not often I get to nitpick @elarlang 😂😂😂

---------

Co-authored-by: Josh Grossman <tghosth@users.noreply.github.com>
Co-authored-by: Elar Lang <elar@hoh.ee>
Updating the wording to correct a spelling error.
* Add rough draft of spellchecker

* Finalize spellchecker

* Cover more files
* Fix cyclonedx output

* Fix cdx output file
ArneBab and others added 9 commits February 11, 2026 08:35
* Replace deprecated URL checker action with maintained fork

gaurav-nelson/github-action-markdown-link-check is explicitly deprecated
and points to tcort/github-action-markdown-link-check as its successor.
The new action is actively maintained by the upstream markdown-link-check
package author and uses the same config file format.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* Test: add intentionally broken link to verify URL checker

This broken link should trigger a failure in the URL checker workflow,
confirming the new action correctly detects dead links. This commit
should be reverted before merging.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* Debug: add verbose output and direct markdown-link-check test

- Add a step that runs markdown-link-check directly (outside Docker)
  to see raw output and verify it detects the broken link
- Disable quiet mode and enable verbose mode on the action step
- This is a temporary debug commit to be reverted

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* Replace Docker-based action with direct markdown-link-check invocation

The tcort/github-action-markdown-link-check Docker action has a known
bug (#553) where markdown-link-check silently fails inside the container,
reporting all links as good without checking anything.

This replaces the action with direct npm installation and invocation of
markdown-link-check, which works correctly on the runner. Also fixes the
PR modified-files detection by using fetch-depth: 0 for proper git diff.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* Remove intentionally broken test link

The URL checker has been verified to correctly detect broken links.
Removing the test link added for debugging.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
* Enhance CONTRIBUTING.md with change control details

Added detailed change control and release process guidelines.

* Fix spelling issue in CONTRIBUTING.md
fix linking from Req. 6.2.9 to 11.2.3
* Retry status-0 URL check failures with curl before failing

The cr.yp.to links consistently fail with status 0 (connection
failure) from GitHub Actions runners despite being valid URLs.

- Increase markdown-link-check timeout from default 10s to 30s
- Add a retry step that re-checks status-0 failures using curl
  with retries, so genuine dead links still fail but servers that
  don't respond to the Node.js HTTP client get a second chance

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* Fix pipefail: tee was swallowing markdown-link-check exit code

Adding `| tee` to capture output caused the pipeline exit code to
always be 0 (from tee), so link check failures were silently ignored.
Adding `set -o pipefail` ensures the pipeline fails when
markdown-link-check fails.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* Use continue-on-error so curl retry can rescue the job

The `if: failure()` approach ran the retry step but couldn't change
the job outcome. Using `continue-on-error: true` with step ID lets
the retry step determine the final pass/fail result.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
…ent (#3348)

* Initial plan

* Remove Jim Manico as project leader, add acknowledgement of previous leadership (#3347)

Co-authored-by: tghosth <13623828+tghosth@users.noreply.github.com>

* Update Jim Manico acknowledgement to reflect full tenure as Project Lead (4.0 through early 5.0)

Co-authored-by: tghosth <13623828+tghosth@users.noreply.github.com>

* Clarify Jim Manico's full involvement in ASVS from version 1.0

Co-authored-by: tghosth <13623828+tghosth@users.noreply.github.com>

* Extend Jim Manico acknowledgement through to after the release of ASVS 5.0

Co-authored-by: tghosth <13623828+tghosth@users.noreply.github.com>

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: tghosth <13623828+tghosth@users.noreply.github.com>
* Remove expired supporters

Updated supporter logos and links in the SUPPORTERS.md file.

* Remove commented-out supporter logos

Removed commented-out supporter logos from the document.
The existing CycloneDX export did not properly validate against the spec. This change corrects that and includes a few other minor improvements.

Co-authored-by: Josh Grossman <tghosth@users.noreply.github.com>
* Add files via upload

* Add files via upload

* Add files via upload

* Add files via upload

* Update 0x00-Header.yaml

* Update 0x01-Frontispiece.md

* Update 0x01-Frontispiece.md

* Update 0x01-Frontispiece.md

* Update 0x02-Preface.md

* Update 0x03-What-is-the-ASVS.md

* Update 0x04-Assessment_and_Certification.md

* Update 0x05-For-Users-Of-4.0.md

* Update 0x10-V1-Encoding-and-Sanitization.md

* Update 0x11-V2-Validation-and-Business-Logic.md

* Update 0x12-V3-Web-Frontend-Security.md

* Update 0x12-V3-Web-Frontend-Security.md

* Add files via upload

* Update 0x15-V6-Authentication.md

* Add files via upload

* Update 0x14-V5-File-Handling.md

* Update 0x16-V7-Session-Management.md

* Update 0x17-V8-Authorization.md

* Update 0x18-V9-Self-contained-Tokens.md

* Update 0x19-V10-OAuth-and-OIDC.md

* Update 0x19-V10-OAuth-and-OIDC.md

* Update 0x19-V10-OAuth-and-OIDC.md

* Update 0x19-V10-OAuth-and-OIDC.md

* Update 0x20-V11-Cryptography.md

* Update 0x00-Header.yaml

* Update 0x01-Frontispiece.md

* Update 0x02-Preface.md

* Update 0x03-What-is-the-ASVS.md

* Update 0x04-Assessment_and_Certification.md

* Update 0x05-For-Users-Of-4.0.md

* Update 0x10-V1-Encoding-and-Sanitization.md

* Update 0x11-V2-Validation-and-Business-Logic.md

* Update 0x12-V3-Web-Frontend-Security.md

* Update 0x13-V4-API-and-Web-Service.md

* Update 0x14-V5-File-Handling.md

* Update 0x15-V6-Authentication.md

* Update 0x15-V6-Authentication.md

* Update 0x15-V6-Authentication.md

* Update 0x15-V6-Authentication.md

* Update 0x16-V7-Session-Management.md

* Update 0x17-V8-Authorization.md

* Update 0x18-V9-Self-contained-Tokens.md

* Update 0x17-V8-Authorization.md

* Update 0x16-V7-Session-Management.md

* Update 0x19-V10-OAuth-and-OIDC.md

* Update 0x20-V11-Cryptography.md

* Update 0x21-V12-Secure-Communication.md

* Update 0x22-V13-Configuration.md

* Update 0x23-V14-Data-Protection.md

* Update 0x24-V15-Secure-Coding-and-Architecture.md

* Update 0x25-V16-Security-Logging-and-Error-Handling.md

* Update 0x26-V17-WebRTC.md

* Update 0x26-V17-WebRTC.md

* Update 0x26-V17-WebRTC.md

* Update 0x26-V17-WebRTC.md

* Update 0x92-Appendix-C_Cryptography.md

* Update 0x94-Appendix-E_Contributors.md

* Delete 5.0/en directory

* Delete 5.0/fa directory

* Delete 5.0/mappings directory

* Add files via upload

---------

Co-authored-by: Josh Grossman <tghosth@users.noreply.github.com>
@tghosth
tghosth force-pushed the v5.0.0_fa branch 2 times, most recently from 1b58c19 to eab3329 Compare July 16, 2026 12:44
@tghosth

tghosth commented Jul 19, 2026

Copy link
Copy Markdown
Collaborator Author

Hi @MaknaSEO, @kaligonj3959-max

Thanks for your efforts on this. A few requests before we can get this merged.

  1. Please can you check that the PDF output looks ok.
  2. Please can you check that the other outputs look ok.
  3. I noticed that a bunch of the headings were not translated. Was that deliberate? If not, please can you open a PR on this branch to fix those and any other issues.

(Internal note, we are up to step 7 on the integration workflow)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.