@reltio/interactions
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 |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Consistent across all versions of this internal Reltio package; not a malware signal here. | ai | |
| provenance | no-provenance | AI (provenance): Internal org package; no provenance across all versions, stable pattern. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal org package; missing metadata is expected for private/internal npm packages with 2200+ versions. | ai | |
| phantom-deps | phantom-dep:@reltio/mdm-sdk | AI (phantom-deps): Same-org scoped dep; phantom-dep heuristic unreliable for bundled packages (main: bundle.js). | ai | |
| phantom-deps | phantom-dep:@reltio/components | AI (phantom-deps): Same-org scoped dep; phantom-dep heuristic unreliable for bundled packages (main: bundle.js). | ai | |
| phantom-deps | phantom-dep:@reltio/mdm-module | AI (phantom-deps): Same-org scoped dep; phantom-dep heuristic unreliable for bundled packages (main: bundle.js). | ai |
Versions (showing 51 of 154)
| Version | Deps | Published |
|---|---|---|
| 1.4.2310 | 3 / 0 | |
| 1.4.2309 | 3 / 0 | |
| 1.4.2308 | 3 / 0 | |
| 1.4.2307 | 3 / 0 | |
| 1.4.2306 | 3 / 0 | |
| 1.4.2305 | 3 / 0 | |
| 1.4.2304 | 3 / 0 | |
| 1.4.2303 | 3 / 0 | |
| 1.4.2302 | 3 / 0 | |
| 1.4.2301 | 3 / 0 | |
| 1.4.2300 | 3 / 0 | |
| 1.4.2299 | 3 / 0 | |
| 1.4.2298 | 3 / 0 | |
| 1.4.2297 | 3 / 0 | |
| 1.4.2296 | 3 / 0 | |
| 1.4.2295 | 3 / 0 | |
| 1.4.2294 | 3 / 0 | |
| 1.4.2293 | 3 / 0 | |
| 1.4.2292 | 3 / 0 | |
| 1.4.2291 | 3 / 0 | |
| 1.4.2290 | 3 / 0 | |
| 1.4.2289 | 3 / 0 | |
| 1.4.2288 | 3 / 0 | |
| 1.4.2287 | 3 / 0 | |
| 1.4.2286 | 3 / 0 | |
| 1.4.2285 | 3 / 0 | |
| 1.4.2284 | 3 / 0 | |
| 1.4.2283 | 3 / 0 | |
| 1.4.2282 | 3 / 0 | |
| 1.4.2281 | 3 / 0 | |
| 1.4.2280 | 3 / 0 | |
| 1.4.2279 | 3 / 0 | |
| 1.4.2278 | 3 / 0 | |
| 1.4.2277 | 3 / 0 | |
| 1.4.2276 | 3 / 0 | |
| 1.4.2275 | 3 / 0 | |
| 1.4.2274 | 3 / 0 | |
| 1.4.2273 | 3 / 0 | |
| 1.4.2272 | 3 / 0 | |
| 1.4.2271 | 3 / 0 | |
| 1.4.2270 | 3 / 0 | |
| 1.4.2269 | 3 / 0 | |
| 1.4.2268 | 3 / 0 | |
| 1.4.2267 | 3 / 0 | |
| 1.4.2266 | 3 / 0 | |
| 1.4.2265 | 3 / 0 | |
| 1.4.2261 | 3 / 0 | |
| 1.4.2260 | 3 / 0 | |
| 1.4.2259 | 3 / 0 | |
| 1.4.2258 | 3 / 0 | |
| 1.4.2257 | 3 / 0 |
v1.4.2310
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2309
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2308
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2307
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2306
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2305
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2304
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2303
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2302
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2301
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2300
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2299
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2298
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2297
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2296
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2295
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2294
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 (egorshkov) than the most recent previously approved version (reltio-ui-coe) on 2026-04-23, but egorshkov 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.
v1.4.2293
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2292
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2291
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2290
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2289
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2288
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2287
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2286
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2285
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2284
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2283
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2282
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2281
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2280
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2279
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2278
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2277
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2276
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2275
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2274
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2273
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2272
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2271
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2270
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2269
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2268
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2267
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 (reltio-ui-coe) than the most recent previously approved version (vitaly.gerasev) on 2026-01-27, but reltio-ui-coe 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.
v1.4.2266
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 (reltio-ui-coe) than the most recent previously approved version (vitaly.gerasev) on 2026-01-23, but reltio-ui-coe 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.
v1.4.2265
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 (reltio-ui-coe) than the most recent previously approved version (vitaly.gerasev) on 2026-01-23, but reltio-ui-coe 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.
v1.4.2261
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2260
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2259
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2258
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2257
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.