Kenapa GitHub Dork Penting
Banyak organisasi menempatkan dokumen publik di GitHub: SECURITY.md, CHANGELOG, ROADMAP, CONTRIBUTING, workflow CI/CD, hingga issue/PR bertema rilis. Dengan GitHub dork (pencarian lanjutan di GitHub), kita dapat:
Memahami arsitektur dan keputusan teknis (ADR, Architecture).
Melihat timeline rilis, deprecations, dan kebijakan integrasi (API/SDK) yang dipublikasikan resmi. Menganalisis proses (review, CODEOWNERS, linting, matrix build) tanpa menyentuh data sensitif.
Dasar-Dasar Pencarian Lanjutan (Qualifier yang Stabil)
Qualifier | Fungsi | Contoh singkat |
---|---|---|
org: |
Batasi ke organisasi | org:example |
user: |
Batasi ke pengguna | user:exampledev |
repo: |
Batasi ke satu repo | repo:example/app |
in: |
Bidang (name , description , readme , title , body ) |
in:readme "API reference" |
path: |
Filter direktori | repo:example/app path:docs/ |
filename: |
Nama file tepat | filename:SECURITY.md org:example |
language: |
Bahasa pemrograman | language:Go org:example |
extension: |
Ekstensi file | extension:md path:docs/ |
is: |
issue , pr , open , closed , merged , archived |
is:pr is:merged org:example |
label: |
Label issue/PR | label:security org:example |
author: assignee: mentions: |
Berdasar aktor | author:alice is:pr org:example |
created: updated: pushed: |
Filter waktu | updated:>=2025-01-01 org:example |
topic: |
Topic repo | topic:sre org:example |
stars: forks: size: |
Opsional kurasi | stars:>100 org:example |
Tips akurasi:
Gabungkan qualifier untuk presisi (org + path + filename).
Gunakan updated:/pushed: untuk kebaruan.
Untuk issue/PR, tambahkan is:open/is:closed/is:merged sesuai kebutuhan.
Area artefak yang “aman” atau harus dicek:
1. Kebijakan & tata kelola: SECURITY.md, CONTRIBUTING.md, CODE_OF_CONDUCT.md, SUPPORT.md, MAINTAINERS.md.
2. Arsitektur & desain: ARCHITECTURE.md, ADR, docs/architecture/system-design.
3. Rilis & perubahan: CHANGELOG.md, PR berjudul “release notes”, migration/upgrade guide.
4. Proses & toolchain: .github/workflows/*.yml, CODEOWNERS, aturan lint/format.
5. Roadmap & RFC: ROADMAP.md, issue berlabel roadmap, PR/issue berjudul RFC/proposal.
6. API & integrasi (dokumen): OpenAPI/Swagger, rate limit, webhook signature.
Peta Kebutuhan Recon → Pola Query
Kebutuhan | Apa yang dicari | Contoh pola |
---|---|---|
Kebijakan keamanan & pelaporan | SECURITY, disclosure, bug bounty | org:example (filename:SECURITY.md OR "responsible disclosure" in:file) |
Proses kontribusi & kode etik | CONTRIBUTING, CODE_OF_CONDUCT | org:example (filename:CONTRIBUTING.md OR filename:CODE_OF_CONDUCT.md) |
Arsitektur & keputusan desain | ARCHITECTURE, ADR, system design | org:example (filename:ARCHITECTURE.md OR "Architecture Decision Record") |
Rilis & perubahan | CHANGELOG, release notes, breaking change | org:example (filename:CHANGELOG.md OR in:title "release notes") is:pr |
Deprecation & migrasi | deprecation, migration/upgrade guide | repo:example/app updated:>=2025-01-01 in:file ("migration guide" OR "upgrade guide") |
API & integrasi | OpenAPI/Swagger, rate limit, webhooks | org:example path:docs/ in:file ("OpenAPI" OR "Swagger" OR "rate limit" OR webhook) |
Proses CI/CD | GitHub Actions workflows, matrix | org:example path:.github/workflows extension:yml in:file "uses:" |
Tata kelola repo | CODEOWNERS, maintainers | org:example filename:CODEOWNERS in:file |
Roadmap & prioritas | ROADMAP, milestone, RFC/proposal | org:example (filename:ROADMAP.md OR in:title roadmap) OR (is:issue in:title (RFC OR proposal)) |
Template Query:
1) Dokumen Kebijakan & Proses
org:example (filename:SECURITY.md OR filename:CONTRIBUTING.md OR filename:CODE_OF_CONDUCT.md OR filename:SUPPORT.md OR filename:MAINTAINERS.md)
2) Arsitektur & ADR
org:example (filename:ARCHITECTURE.md OR "Architecture Decision Record" OR filename:ADR.md) path:docs/ extension:md
org:example in:readme ("architecture" OR "system design" OR "ADR")
3) Rilis, Deprecation, Migrasi
org:example (filename:CHANGELOG.md OR "release notes" in:title) extension:md
org:example in:title "release notes" is:pr
repo:example/app updated:>=2025-01-01 in:file ("deprecation" OR "breaking change" OR "migration guide" OR "upgrade guide")
4) Issue & PR untuk Insight Non-Sensitif
org:example is:issue is:open label:bug in:title (timeout OR crash OR overflow)
org:example is:issue in:title (oauth OR oidc OR "rate limit")
org:example is:pr in:title (refactor OR harden OR "security policy")
5) Proses & Toolchain (CI/CD)
org:example path:.github/workflows extension:yml in:file "uses:"
org:example filename:CODEOWNERS in:file
6) API & Integrasi (Dokumentasi Resmi)
org:example path:docs/ in:file ("OpenAPI" OR "Swagger" OR "API reference" OR "rate limit" OR "webhook")
7) Roadmap, RFC, Proposal
org:example (filename:ROADMAP.md OR in:title roadmap)
org:example is:issue in:title ("RFC" OR "proposal")
org:example in:file ("milestone" OR "Q1" OR "quarter") path:docs/
Dengan qualifier yang tepat, pola pencarian fokus artefak publik, dan disiplin validasi konteks, Anda memperoleh gambaran teknis yang mau dicapai.