Explain security rationale for custom packages opt-in - #1247
Merged
Merged
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Contributor
Documentation validation✅ All blocking checks passed. Component system0 finding(s) across the corpus. Findings on lines this pull request touched are annotated inline in Files changed. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Reframes the "Experimental: custom dependencies" section in the data-apps download page to explain why the feature is flagged off by default: it's a security decision each org opts into, because enabling it lets apps pull third-party packages from public npm into the build sandbox.
Adds a short bulleted list covering:
manage:DataAppDependencyupload permission is admin-only by default.--frozen-lockfile --ignore-scripts, no credentials in the build, egress limited to npm).Trimmed the follow-up "Security model" paragraph to avoid duplicating the guardrails now covered above; it now focuses on the local
.npmrcand self-host env vars (LIGHTDASH_APP_DEPENDENCY_MIN_RELEASE_AGE_DAYS,LIGHTDASH_APP_DEPENDENCY_REGISTRY_HOSTS).Generated by Mintlify Agent.
Requested by: jess@lightdash.com via Slack
Mintlify session: slack_1789141655.887279_C0AM8D5UUR5