Skip to content

アプリケーションセキュリティ検証標準を日本語化します。

active 2023-08-152026-08-13 (UTC)

Partial coverage20,529 / 26,285 hourly files (78%) · 2 absent upstream · 5,753 failed, retryable2023-08-152026-08-14 (UTC)— sampled evenly across the window, so rankings and trends hold; absolute counts scale up.
Events
7.3K
Pushes
601
Pull requests
597
Issues
649
Stars
592
Forks
136

Activity over time

Daily event counts in the loaded window

Line chart, 1095 days from 2023-08-15 to 2026-08-13. Pushes: 601 total, peak 24 in a day. Pull requests: 597 total, peak 33 in a day. Issues: 649 total, peak 18 in a day. Comments: 3,789 total, peak 142 in a day. Stars: 592 total, peak 15 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.

Top contributors

Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity

ContributorContributionsPushesPRsComments
elarlang1.9K1602141.1K
tghosth1.8K385275889
jmanico7393828561
randomstuff593017448
TobiasAhnoff1240198
ajayojha1150084
csfreak921150486
EnigmaRosa860866
ImanSharaf830258
ryarmst720755
octo-reminder[bot]370037
oleksiidov310619
ike301457
clallier94270016
kkshitish9250023
inaz0190010
danielcuthbert17219
narfbg140111
sydseter140014
meghanjacquot130013

Recent activity

Latest issues, pull requests and releases

  • Issue comment#3379tghosth2026-07-19 06:37
    Bump actions/upload-artifact from 4.3.0 to 7.0.1
  • Issue#3364elarlang2026-06-24 10:52
    Clarification of language around HSTS
  • Issue comment#3360cmlh2026-05-30 22:53
    Improve clarity of TLS version requirements in V9.1.3
  • Issue comment#3182vhnogueira92026-05-21 00:16
    Portuguese (Brazil) translation of ASVS v5.0.0
  • Pull request#3357kaligonj3959-max2026-04-19 00:44
  • Pull request#3355stevespringett2026-04-14 21:40
  • Issue comment#3352elarlang2026-04-03 07:05
    Proposal: add requirements to verify correct implementation of OAuth PAR and JAR
  • Issue comment#3352narfbg2026-04-02 19:47
    Proposal: add requirements to verify correct implementation of OAuth PAR and JAR
  • Issue comment#3346elarlang2026-03-18 09:01
    proposal: add requirement to verify that using a sanitization is an accepted solution for that data or flow
  • Issue comment#3346ajayojha2026-03-18 08:20
    proposal: add requirement to verify that using a sanitization is an accepted solution for that data or flow
  • Issue#3347tghosth2026-03-17 07:05
    Remove jmanico as leader and contributor from standard
  • Issue comment#3346ajayojha2026-03-15 11:05
    proposal: add requirement to verify that using a sanitization is an accepted solution for that data or flow
  • Issue comment#3335J-XL2026-03-13 21:26
    Refine explanation of "sanitization"
  • Issue comment#3346elarlang2026-03-13 08:11
    proposal: add requirement to verify that using a sanitization is an accepted solution for that data or flow
  • Issue comment#3346elarlang2026-03-12 19:36
    proposal: add requirement to verify that using a sanitization is an accepted solution for that data or flow
  • Issue comment#3346elarlang2026-03-12 12:07
    proposal: add requirement to verify that using a sanitization is an accepted solution for that data or flow
  • Issue comment#3335jmanico2026-03-11 22:12
    Refine explanation of "sanitization"
  • Issue comment#3346jmanico2026-03-11 14:12
    proposal: add requirement to verify that using a sanitization is an accepted solution for that data or flow
  • Issue comment#3335ajayojha2026-03-11 03:14
    Refine explanation of "sanitization"
  • Issue comment#3346narfbg2026-03-10 21:07
    proposal: add requirement to verify that using a sanitization is an accepted solution for that data or flow
  • Issue comment#3231elarlang2026-03-09 08:37
    Clarification: 1.3.1 WYSIWYG
  • Issue comment#3335ajayojha2026-03-09 04:12
    Refine explanation of "sanitization"
  • Issue comment#3335jmanico2026-03-08 23:20
    Refine explanation of "sanitization"
  • Issue comment#3338elarlang2026-03-08 08:36
    Phishing and/or visual deception protections
  • Issue#3338tghosth2026-03-08 08:14
    Phishing and/or visual deception protections

Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 592 stars here means stars gained during the window, not the repo's star count.