audit.sh: add a GDPR compliance check for repos that handle personal data
まだ誰も着手していません。
評価
- 難易度
- 4/5
- 見積もり時間
- 3〜5日
- 初心者へのやさしさ
- 56/100
調査の方向性
Start with scripts/audit.sh, the existing optional site-file check, and scripts/lib/detect-privacy.sh; inspect tests/run.sh for fixture conventions. Add checks for the listed privacy signals, notices and contacts, and the consent reminder for tracking signals, while skipping dependency, lock and build output. Done means the specified fixtures pass, ShellCheck passes, Bash 3.2 works, and output describes the heuristic without claiming compliance or giving legal advice.
索引モデルが issue の本文から書いたものです。
説明
Problem
scripts/audit.sh checks for the standard OSS files and has no privacy check at all. A repo can load Google Analytics or collect sign-ups from EU visitors, have no privacy notice, and still get a perfect audit score. GDPR Article 13 requires telling people what is collected at the point of collection, so this is a gap in a tool whose job is getting a repo ready to go public.
Proposed check
Add a GDPR check that runs only when the repo shows signs of handling personal data, the same way the Optional site-file block only prints when detect_site_framework finds a site. Put detection in scripts/lib/detect-privacy.sh.
Signals to look for in manifests and source:
| Signal | Examples |
|---|---|
| Analytics and tracking | @vercel/analytics, posthog-js, mixpanel, @segment/*, @amplitude/*, react-ga*, gtag(, googletagmanager.com, connect.facebook.net, hotjar |
| Accounts and user data | @supabase/*, firebase, next-auth, @auth/*, @clerk/* |
| Error tracking | @sentry/* |
| Third-party assets fetched by the visitor's browser | fonts.googleapis.com |
When a signal is found, report:
- Whether a privacy notice exists (
PRIVACY.md, or aprivacypage or route for a detected site). - Whether a privacy contact is named in it.
- For analytics and tracking signals, a reminder to confirm consent is collected before non-essential cookies are set. A scan cannot prove this, so it stays a prompt.
Each finding names the signal and the file it was found in, so the result can be checked by hand.
Limits
This reports signals. It is not a legal review, and it can't tell whether a project is compliant. The output must say so and must never print "GDPR compliant".
Done when
- A fixture with
@vercel/analyticsand no privacy notice gets a warning naming the package and the file. - The same fixture with a
PRIVACY.mdgets no missing-notice warning. - A fixture with no signals prints nothing new, and its score is unchanged.
node_modules, lockfiles, and build output are not scanned.- The output states that this is a heuristic and not legal advice.
tests/run.shcovers the cases above,shellcheckpasses, and the script runs on bash 3.2.
A templates/PRIVACY.md that apply.sh can generate is a sensible follow-up, but it is out of scope here.
- 主要言語
- Shell
- スター
- 16
- フォーク
- 9
- 平均マージ
- 1日 17時間
- マージ済み PR（30日）
- 1
環境構築
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートあり
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
CreativesLibrary/oss-launch のほかの issue
-
enhancement
難易度 2/5 1〜3時間 初心者へのやさしさ 76/100
-
enhancement
難易度 2/5 1〜3時間 初心者へのやさしさ 77/100
-
dependencies enhancement good first issue
難易度 2/5 1〜3時間 初心者へのやさしさ 83/100
-
enhancement
難易度 2/5 1〜3時間 初心者へのやさしさ 76/100
-
bug
難易度 2/5 1〜3時間 初心者へのやさしさ 82/100
CreativesLibrary/oss-launch の issue をすべて見る
似ている issue
-
DeclareMiningJob.wtxid_list should be specified to be in block order対応中かも このイシューにリンクされたプルリクエストがオープン中、またはマージ済みです。 オープン
難易度 1/5 1時間未満 初心者へのやさしさ 84/100
stratum-mining/sv2-spec#253 ·
-
area:linux source:reader type:content-error
難易度 1/5 1時間未満 初心者へのやさしさ 84/100
stephrobert/blog-roadmap#169 ·
-
難易度 2/5 1〜3時間 初心者へのやさしさ 68/100
cisagov/skeleton-docker#322 ·
-
bot-found bug priority: P3
難易度 2/5 1〜3時間 初心者へのやさしさ 83/100
madenvel/KalinkaPlayer#543 ·
-
難易度 1/5 1時間未満 初心者へのやさしさ 65/100