All @medplum/core versions

@medplum/[email protected] rejected Risk: 25 No license

@medplum/core @2.1.26

rejected
This version was rejected. It did not pass GreenFlagged's security review and is not served by the registry. The findings and risk dispositions below explain why.
npm Repository Homepage Tarball
25
Risk Score
—
License
No
Install Scripts
0
Dependencies
3
Dev Dependencies
443.1 KB
Package Size
Published

Maintainers

codyebbersonreshmakhrahul1

Keywords

medplumfhirhealthcareinteroperabilityjsonserializationhl7standardsclinicaldstu2stu3r4normative

Dev Dependencies (3)

PackageConstraintRegistry Status
@medplum/fhirtypes * auto_approved
jest-websocket-mock 2.5.0 auto_approved
@medplum/definitions * auto_approved

Changes from v5.0.15

Dependency Changes

Script Changes

- lint- lint:fix

File Changes

0 added 1 removed 8 modified size delta: -1338.4 KB

Risk Dispositions (1 applicable to this version, 0 other)

Accepted rules are downgraded to INFO on future analyses; rejected rules escalate to CRITICAL.

Rule Source Disposition Author Reason
regressed-provenance provenance reject AI AI (provenance): Provenance regression on a high-impact package is a strong supply-chain signal; should generalize until CI/CD publishing is restored.

SAST Findings (2)

HIGH Provenance attestation missing — previous versions had it provenance

This version was published without provenance, but prior versions were published via CI/CD with attestations. This is a strong signal of a potential account compromise or unauthorized publish. The axios attack (March 2026) exhibited exactly this pattern.

INFO Publisher changed: GitHub Actions → codyebberson (on 2026-02-23, known maintainer) provenance

This version was published by a different npm account (codyebberson) than the most recent previously approved version (GitHub Actions) on 2026-02-23, but codyebberson is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

Review Summary

Risk score: 25. Findings: 1 high (+25), 2 info (+0).

Commit: a1b33b73f169 Browse source

Published to npm: