Improve npm package installation security - #40
Open
microbit-grace wants to merge 3 commits into
Open
Conversation
microbit-grace
force-pushed
the
npm-update
branch
from
July 27, 2026 09:58
11368c3 to
970e46b
Compare
microbit-grace
marked this pull request as draft
July 27, 2026 10:34
Author
|
Broke Update: Fixed by dcc23c1 |
microbit-grace
marked this pull request as ready for review
July 27, 2026 10:53
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
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.
.npmrc:
package.json:
npm idoesn't fail. fsevents scripts have been allowed. keytar scripts have been disallowed.npm run buildin browser-pyright works in node 24.package-lock.json files in all 4 packages have been regenerated.
validation.yml - Updated node and npm versions, though in practice, they do not run in this forked repo (guarded by
github.repository == 'microsoft/pyright').