docs(repo): safeguard against supply chain attacks#2382
Merged
Conversation
mandarini
force-pushed
the
docs/safeguard-npm
branch
from
e8636d4 to
4e0e86a
Compare
staaldraad
previously approved these changes
May 20, 2026
staaldraad
approved these changes
May 21, 2026
jgoux
approved these changes
May 21, 2026
laktek
reviewed
May 21, 2026
|
|
||
| ### Deno / Edge Functions | ||
|
|
||
| Deno has an unstable `--minimum-dependency-age` flag that accepts minutes, an ISO-8601 duration, or an absolute RFC3339 cutoff: |
Contributor
There was a problem hiding this comment.
This wouldn't work with Edge Functions and also an unstable feature. Maybe we should leave this out?
Contributor
Author
There was a problem hiding this comment.
Ok, I'll put in a follow up to remove. We do acknowledge at least that it's unstable 😓
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
4 participants
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.
Add user guide on how users can safeguard against npm supply chain attacks