← Home

@openmrs/esm-framework

npm Repository Homepage
3
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

mogoodrichopenmrs-botrkorytkowskidjazayerijoeldenningmksdbrandonesjdickbmamlindkibetmdubeydennisforthewinibacher

Keywords

openmrsframeworkfrontenduimicrofrontends

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata no-description AI (npm-metadata): Well-known package; missing description is cosmetic, not a risk signal. ai
bogus-package bogus-package AI (bogus-package): Established framework package with 93 approved dependents; README/description signals are false positives. ai
dependencies unvetted-dep:@openmrs/esm-styleguide AI (dependencies): Co-released monorepo sibling; always published at the same version as the parent package. ai
dependencies unvetted-dep:@openmrs/esm-utils AI (dependencies): Co-released monorepo sibling; always published at the same version as the parent package. ai
dependencies unvetted-dep:@openmrs/esm-expression-evaluator AI (dependencies): Co-released monorepo sibling; always published at the same version as the parent package. ai
dependencies unvetted-dep:@openmrs/esm-react-utils AI (dependencies): Co-released monorepo sibling; always published at the same version as the parent package. ai
dependencies unvetted-dep:@openmrs/esm-globals AI (dependencies): Co-released monorepo sibling; always published at the same version as the parent package. ai

Versions (showing 3 of 3)

Version Deps Published
9.0.2 18 / 15
9.0.1 18 / 15
9.0.0 18 / 15

v9.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v9.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v9.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.