-
Notifications
You must be signed in to change notification settings - Fork 0
docs(examples): use semantic owned database names #1086
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
seonghobae
wants to merge
10
commits into
develop
Choose a base branch
from
fix/fixed-example-semantic-database-names
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
7dba796
docs(example): use semantic project database names
seonghobae a814b2c
test(example): pin semantic database naming contract
seonghobae 37085e5
docs(changelog): record fixed-example naming repair
seonghobae d5c010e
test(example): pin validation and API compatibility
seonghobae fcd2856
docs(example): validate inputs and preserve API surface
seonghobae 54bfdf7
test(example): require auth before admin input handling
seonghobae 72ebb83
docs(example): authenticate before admin input handling
seonghobae b1812db
test(example): require semantic names in vulnerable fixture
seonghobae 948756f
docs(example): decouple vulnerable fixture from generic naming
seonghobae e8a6b7a
docs(changelog): cover both security examples
seonghobae File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,5 @@ | ||
| ### Documentation | ||
|
|
||
| - Updated the fixed and intentionally vulnerable Next.js/Supabase security examples so organization-owned project schema and internal identifiers use bounded-context-specific multiword names (`project_records`, `project_id`, `owner_user_id`, `project_name`, `project_payload`) while vendor-owned NextAuth/Supabase/Zod identifiers remain at their adapter boundaries. | ||
| - Preserved the vulnerable fixture's intentional security failures while decoupling them from ambiguous organization-owned naming, so readers do not learn generic database names as part of the vulnerability demonstration. | ||
| - Added regression coverage that prevents either example from reintroducing the previous generic project table and column names, protects the fixed sample's existing API response/path contract, and keeps protected-request authentication/validation ordering explicit. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.