No LICENSE file in the repository
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 69/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- postgresql
- Domain
- documentation
Research direction
Start with the README badge and verify which LICENSE path it links to; the issue does not name a license or provide a file to edit. Review the repository’s existing license related references, then add the license file that accurately covers the project and the three vendored lint queries. Done when the badge points to an existing license and the project’s licensing is recorded honestly.
Written by the indexing model from the issue text.
Description
The README badge links to a LICENSE file that does not exist (GitHub API reports license: null at commit fccca4b1c4d8b48b8ccd69bd6b30e84adcb92975). Could you add one? We vendor three lint queries (0001, 0004, 0009) verbatim in a private project and want to record the license honestly. Thanks for splinter.
- Dominant language
- PLpgSQL
- Stars
- 284
- Forks
- 110
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from supabase/splinter
-
0002_auth_users_exposed false positive: pg_depend join lacks a refclassid filter (cross-catalog OID collision)Possibly taken @tushardev-365 claimed this 94 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
0030_autovacuum_disabled misses tables where autovacuum_enabled is set to off, 0 or noPossibly taken @RaphaelFakhri claimed this 7 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
Proposal: lint for RLS policies whose role lacks the table privilege (policy_without_privilege)Possibly taken @larik15 claimed this 26 days ago. Open
Difficulty 1/5 Under an hour Newbie friendliness 1/100
Maintainers usually reply within 1 day
-
0028/0029 silently report zero findings for projects using a custom PostgREST request rolePossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 4/5 3-5 days Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
0025_public_bucket_allows_listing silently returns zero findings when splinter.public_buckets is unset — undocumented transaction-local contractPossibly taken @sidgaikwad claimed this 47 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 45/100
supabase/splinter#181 · 1 comment ·
Maintainers usually reply within 1 day
All issues in supabase/splinter
Similar issues
-
r-bug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
servo/rust-smallvec#844 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
hiero-ledger/solo-docs#343 ·
Maintainers usually reply within 6 days
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
bnb-chain/bnb-chain.github.io#961 ·
Maintainers usually reply within 1 day
-
community documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 70/100
jim-wyatt/two-computers-one-board#192 ·
Maintainers usually reply within 1 day