Verify npm releases after registry processing - #11
Merged
Merged
Conversation
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.
npm can accept publication while the version is still being processed. Wait up to five minutes for the exact version before validating an anonymous installation. Add a verification-only input so an already submitted immutable version can be checked without republishing it. Verify imports, registry signatures and attestations, and require the downloaded tarball to match the GitHub release byte for byte.
Scope the failed-telemetry browser assertion to the submitted request. A new suggestion can legitimately add another presentation event after sending; the check still requires presentation, acceptance and submission delivery to fail while host submission succeeds exactly once.
Validation: actionlint passed; generated types unchanged; full local SDK checks passed (90 unit, 6 script, 26 source browser, 52 packaged React 18/19 browser tests and consumer builds). The affected React and assistant-ui case passed 10 repeated checks. An independent anonymous installation of public 0.6.4 passed root/server imports and npm signature/attestation verification; its tarball matches v0.6.4 and its generated example builds.