@metriport/shared
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:semver | AI (phantom-deps): semver is declared as a runtime dep with a broad range constraint; phantom detection is a packaging style choice, not a security issue for this package. | ai | |
| phantom-deps | phantom-dep:@medplum/core | AI (phantom-deps): @medplum/core is a legitimate FHIR library dependency; phantom detection reflects indirect import patterns, not a security concern for this package. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.33.5 | 10 / 15 | |
| 0.33.4 | 10 / 15 | |
| 0.33.1 | 10 / 15 | |
| 0.33.0 | 10 / 15 | |
| 0.29.0 | 9 / 13 | |
| 0.28.1 | 9 / 13 | |
| 0.28.0 | 9 / 13 | |
| 0.27.2 | 9 / 13 | |
| 0.27.1 | 9 / 13 | |
| 0.27.0 | 9 / 13 | |
| 0.23.3 | 8 / 12 | |
| 0.23.2 | 8 / 12 | |
| 0.23.1 | 7 / 12 |
v0.33.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.4
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (radmirgaripov) than the most recent previously approved version (jwar44) on 2026-06-06, but radmirgaripov 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.
v0.33.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jwar44) than the most recent previously approved version (rafaelleite) on 2026-06-01, but jwar44 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.
v0.33.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.29.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.28.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.28.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.27.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.27.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.