@reltio/members SEE LICENSE IN LICENSE FILE 51 versions

@reltio/members

npm

51

Versions

SEE LICENSE IN LICENSE FILE

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

egorshkovvitaly.gerasevalexander.leshukovreltio-ui-coemanpreet_hayerandrew.borovin.reltioamith.ravuru

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
semgrep	semgrep:new-function-constructor	AI (semgrep): Fires in bundle.js webpack output; standard bundler pattern for this org's packages.	ai	2026/05/27
dependencies	unvetted-dep:@reltio/mdm-sdk	AI (dependencies): Same-org @reltio scoped dependency; consistent pattern across all versions of this package.	ai	2026/05/26
dependencies	unvetted-dep:@reltio/mdm-module	AI (dependencies): Same-org @reltio scoped dependency; consistent pattern across all versions of this package.	ai	2026/05/26
phantom-deps	phantom-dep:@reltio/components	AI (phantom-deps): Same org scope; likely re-exported or used indirectly via bundle.js.	ai	2026/04/30
bogus-package	bogus-package	AI (bogus-package): Internal enterprise scoped package; missing metadata is expected for org-internal components.	ai	2026/04/30
phantom-deps	phantom-dep:@reltio/mdm-module	AI (phantom-deps): Same org scope; likely re-exported or used indirectly via bundle.js.	ai	2026/04/30
npm-metadata	no-description	AI (npm-metadata): Consistent pattern across @reltio/ org packages; not a malware indicator.	ai	2026/04/30
phantom-deps	phantom-dep:@reltio/mdm-sdk	AI (phantom-deps): Same org scope; likely re-exported or used indirectly via bundle.js.	ai	2026/04/30

Versions (showing 51 of 89)

View all versions

Version	Deps	Published
1.4.108	3 / 0	2026-06-03
1.4.107	3 / 0	2026-05-28
1.4.106	3 / 0	2026-05-28
1.4.105	3 / 0	2026-05-25
1.4.104	3 / 0	2026-05-21
1.4.103	3 / 0	2026-05-19
1.4.102	3 / 0	2026-05-19
1.4.101	3 / 0	2026-05-13
1.4.100	3 / 0	2026-05-07
1.4.99	3 / 0	2026-05-07
1.4.98	3 / 0	2026-05-07
1.4.97	3 / 0	2026-04-30
1.4.96	3 / 0	2026-04-28
1.4.95	3 / 0	2026-04-28
1.4.94	3 / 0	2026-04-23
1.4.93	3 / 0	2026-04-23
1.4.92	3 / 0	2026-04-23
1.4.91	3 / 0	2026-04-21
1.4.90	3 / 0	2026-04-15
1.4.89	3 / 0	2026-04-10
1.4.88	3 / 0	2026-04-08
1.4.87	3 / 0	2026-04-08
1.4.86	3 / 0	2026-04-02
1.4.85	3 / 0	2026-04-02
1.4.84	3 / 0	2026-03-27
1.4.83	3 / 0	2026-03-27
1.4.82	3 / 0	2026-03-24
1.4.81	3 / 0	2026-03-20
1.4.80	3 / 0	2026-03-19
1.4.79	3 / 0	2026-03-13
1.4.78	3 / 0	2026-03-11
1.4.77	3 / 0	2026-03-10
1.4.76	3 / 0	2026-03-04
1.4.75	3 / 0	2026-02-26
1.4.74	3 / 0	2026-02-25
1.4.73	3 / 0	2026-02-25
1.4.72	3 / 0	2026-02-19
1.4.71	3 / 0	2026-02-13
1.4.70	3 / 0	2026-02-06
1.4.69	3 / 0	2026-01-27
1.4.68	3 / 0	2026-01-27
1.4.67	3 / 0	2026-01-27
1.4.66	3 / 0	2026-01-27
1.4.65	3 / 0	2026-01-23
1.4.64	3 / 0	2026-01-23
1.4.60	3 / 0	2025-12-10
1.4.59	3 / 0	2025-12-04
1.4.58	3 / 0	2025-12-04
1.4.57	3 / 0	2025-12-04
1.4.56	3 / 0	2025-12-04
1.4.55	3 / 0	2025-12-02

v1.4.108

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.107

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.106

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.105

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.104

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.103

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.102

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.101

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.100

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.99

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.98

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.97

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.96

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.

v1.4.95

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.94

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.

v1.4.93

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: reltio-ui-coe → egorshkov (on 2026-04-23, known maintainer) provenance

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.92

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.91

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.

v1.4.90

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.89

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.

v1.4.88

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.87

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.

v1.4.86

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.

v1.4.85

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.

v1.4.84

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.

v1.4.83

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.82

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.

v1.4.81

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.

v1.4.80

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.

v1.4.79

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.78

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.

v1.4.77

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.

v1.4.76

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.

v1.4.75

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.

v1.4.74

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.73

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.

v1.4.72

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.71

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.

v1.4.70

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.69

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.

v1.4.68

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.

v1.4.67

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.66

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.65

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.

v1.4.64

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: vitaly.gerasev → reltio-ui-coe (on 2026-01-23, known maintainer) provenance

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.60

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.

v1.4.59

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.58

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.

v1.4.57

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.56

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.

v1.4.55

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.