@reltio/hierarchy
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Internal Reltio package; no provenance is consistent across all versions in this org. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Stable internal org package; missing description is a consistent pattern across versions, not a malware signal. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): Fires in webpack bundle output; standard pattern for this org's UI packages across many versions. | ai | |
| dependencies | unvetted-dep:@reltio/mdm-sdk | AI (dependencies): Same org scope (@reltio); internal dependency consistent with this package's ecosystem. | ai | |
| dependencies | unvetted-dep:@reltio/mdm-module | AI (dependencies): Same org scope (@reltio); internal dependency consistent with this package's ecosystem. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal enterprise component; missing metadata is expected, not a spam/malware indicator given 100-version history. | ai | |
| phantom-deps | phantom-dep:@reltio/mdm-sdk | AI (phantom-deps): Same org scope; phantom-dep heuristic unreliable for bundled internal packages. | ai | |
| phantom-deps | phantom-dep:@reltio/mdm-module | AI (phantom-deps): Same org scope; consistent with bundled internal module pattern. | ai | |
| phantom-deps | phantom-dep:@reltio/components | AI (phantom-deps): Same org scope; consistent with bundled internal component library pattern. | ai |
Versions (showing 14 of 118)
| Version | Deps | Published |
|---|---|---|
| 1.4.14 | 3 / 0 | |
| 1.4.13 | 3 / 0 | |
| 1.4.12 | 3 / 0 | |
| 1.4.11 | 3 / 0 | |
| 1.4.10 | 3 / 0 | |
| 1.4.9 | 3 / 0 | |
| 1.4.8 | 3 / 0 | |
| 1.4.7 | 3 / 0 | |
| 1.4.6 | 3 / 0 | |
| 1.4.5 | 3 / 0 | |
| 1.4.4 | 3 / 0 | |
| 1.4.3 | 3 / 0 | |
| 1.4.2 | 3 / 0 | |
| 1.4.1 | 3 / 0 |
v1.4.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.