@ohif/core
Generic business logic for web-based medical imaging applications
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 |
|---|---|---|---|---|
| publish-pattern | rapid-publish | AI (publish-pattern): High-velocity monorepo with 1007 versions; rapid patch publishes are normal for this package. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): OHIF is a large OSS project; maintainer roster changes are routine and publisher sedghi has a clean track record. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Maintainer removals consistent with normal OSS project churn; no other risk signals present. | ai | |
| dependencies | unvetted-dep:validate.js | AI (dependencies): validate.js is a well-known form validation library; low risk for this established package. | ai | |
| provenance | no-provenance | AI (provenance): Established package with long history; lack of provenance is common and not a security concern here. | ai | |
| phantom-deps | phantom-dep:query-string | AI (phantom-deps): Stable false positive for this bundled package. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): Framework-scoped runtime dep; loaded by convention in bundled output. | ai | |
| phantom-deps | phantom-dep:lodash.isequal | AI (phantom-deps): Stable false positive for this bundled package. | ai | |
| phantom-deps | phantom-dep:react-shepherd | AI (phantom-deps): Stable false positive for this bundled package. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): @ohif/core is a scoped medical imaging library; Levenshtein match to 'cors' is a false positive. | ai | |
| phantom-deps | phantom-dep:lodash.clonedeep | AI (phantom-deps): Stable false positive for this bundled package. | ai | |
| phantom-deps | phantom-dep:isomorphic-base64 | AI (phantom-deps): Stable false positive for this bundled package. | ai | |
| phantom-deps | phantom-dep:immutability-helper | AI (phantom-deps): Stable false positive for this bundled package. | ai | |
| phantom-deps | phantom-dep:dicomweb-client | AI (phantom-deps): Stable false positive for this bundled package. | ai | |
| phantom-deps | phantom-dep:moment | AI (phantom-deps): Large monorepo package; phantom-dep heuristic unreliable for bundled/config-referenced deps. | ai | |
| phantom-deps | phantom-dep:object-hash | AI (phantom-deps): Same as above — stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:shepherd.js | AI (phantom-deps): Bundled via react-shepherd; phantom-dep heuristic fires incorrectly. | ai | |
| phantom-deps | phantom-dep:validate.js | AI (phantom-deps): Stable false positive for this bundled package. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 3.12.4 | 14 / 1 | |
| 3.12.3 | 14 / 1 | |
| 3.12.2 | 14 / 1 | |
| 3.12.1 | 14 / 1 | |
| 3.12.0 | 14 / 1 | |
| 3.11.1 | 14 / 1 | |
| 3.11.0 | 14 / 1 | |
| 3.10.4 | 14 / 1 | |
| 3.10.2 | 14 / 1 |
v3.12.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.