Skip to content

feat: Add guidance about npx/yarn dlx #162

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.

Sign up for GitHub

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

Merged
Gudahtt merged 1 commit into from
Jan 6, 2026
Merged

feat: Add guidance about npx/yarn dlx #162

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion docs/secure-coding-guidelines.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -121,7 +121,9 @@ The guidelines in this policy were gathered primarily from the [OWASP Top 10](ht

#### Dependency Integrity

- Use a lockfile or pinned dependencies to maintain control over which version of each dependency is used
- Use a lockfile to maintain control over which version of each dependency is used
Copy link
Member Author

@Gudahtt Gudahtt Jan 6, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I removed "or pinned dependencies" because pinning dependencies is not an acceptable alternative to using a lockfile.

Pinning makes sense to do in some situations, but we should always have a lockfile.

- Do not use `npx` or `yarn dlx`
- These commands do not update the lockfile, so we have no control over which versions are installed. This leaves us vulnerable to supply-chain attacks.

#### Avoid Deprecated and Unmaintained Packages

Expand Down
Loading