← Home

@reltio/interactions

npm
100
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

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

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 100 of 368)

Version Deps Published
1.4.2223 3 / 0
1.4.2222 3 / 0
1.4.2221 3 / 0
1.4.2220 3 / 0
1.4.2219 3 / 0
1.4.2218 3 / 0
1.4.2217 3 / 0
1.4.2216 3 / 0
1.4.2215 3 / 0
1.4.2214 3 / 0
1.4.2213 3 / 0
1.4.2212 3 / 0
1.4.2211 3 / 0
1.4.2210 3 / 0
1.4.2209 3 / 0
1.4.2208 3 / 0
1.4.2207 3 / 0
1.4.2206 3 / 0
1.4.2205 3 / 0
1.4.2204 3 / 0
1.4.2203 3 / 0
1.4.2202 3 / 0
1.4.2201 3 / 0
1.4.2200 3 / 0
1.4.2199 3 / 0
1.4.2198 3 / 0
1.4.2197 3 / 0
1.4.2196 3 / 0
1.4.2195 3 / 0
1.4.2194 3 / 0
1.4.2193 3 / 0
1.4.2192 3 / 0
1.4.2191 3 / 0
1.4.2190 3 / 0
1.4.2189 3 / 0
1.4.2188 3 / 0
1.4.2187 3 / 0
1.4.2186 3 / 0
1.4.2185 3 / 0
1.4.2184 3 / 0
1.4.2183 3 / 0
1.4.2182 3 / 0
1.4.2181 3 / 0
1.4.2180 3 / 0
1.4.2179 3 / 0
1.4.2178 3 / 0
1.4.2177 3 / 0
1.4.2176 3 / 0
1.4.2175 3 / 0
1.4.2174 3 / 0
1.4.2173 3 / 0
1.4.2172 3 / 0
1.4.2171 3 / 0
1.4.2170 3 / 0
1.4.2169 3 / 0
1.4.2168 3 / 0
1.4.2167 3 / 0
1.4.2166 3 / 0
1.4.2165 3 / 0
1.4.2164 3 / 0
1.4.2163 3 / 0
1.4.2162 3 / 0
1.4.2161 3 / 0
1.4.2160 3 / 0
1.4.2159 3 / 0
1.4.2158 3 / 0
1.4.2157 3 / 0
1.4.2156 3 / 0
1.4.2155 3 / 0
1.4.2154 3 / 0
1.4.2153 3 / 0
1.4.2152 3 / 0
1.4.2151 3 / 0
1.4.2150 3 / 0
1.4.2149 3 / 0
1.4.2148 3 / 0
1.4.2147 3 / 0
1.4.2146 3 / 0
1.4.2145 3 / 0
1.4.2144 3 / 0
1.4.2143 3 / 0
1.4.2142 3 / 0
1.4.2141 3 / 0
1.4.2140 3 / 0
1.4.2139 3 / 0
1.4.2138 3 / 0
1.4.2137 3 / 0
1.4.2136 3 / 0
1.4.2135 3 / 0
1.4.2134 3 / 0
1.4.2133 3 / 0
1.4.2132 3 / 0
1.4.2131 3 / 0
1.4.2128 3 / 0
1.4.2127 3 / 0
1.4.2126 3 / 0
1.4.2125 3 / 0
1.4.2124 3 / 0
1.4.2123 3 / 0
1.4.2122 3 / 0
Showing 100 of 368 Next page →

v1.4.2153

1 finding
INFO No provenance attestation provenance

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

v1.4.2152

1 finding
INFO No provenance attestation provenance

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

v1.4.2151

1 finding
INFO No provenance attestation provenance

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

v1.4.2150

1 finding
INFO No provenance attestation provenance

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

v1.4.2149

1 finding
INFO No provenance attestation provenance

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

v1.4.2148

1 finding
INFO No provenance attestation provenance

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

v1.4.2147

1 finding
INFO No provenance attestation provenance

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

v1.4.2146

1 finding
INFO No provenance attestation provenance

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

v1.4.2145

1 finding
INFO No provenance attestation provenance

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

v1.4.2144

1 finding
INFO No provenance attestation provenance

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

v1.4.2143

1 finding
INFO No provenance attestation provenance

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

v1.4.2142

1 finding
INFO No provenance attestation provenance

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

v1.4.2141

1 finding
INFO No provenance attestation provenance

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

v1.4.2140

1 finding
INFO No provenance attestation provenance

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

v1.4.2139

1 finding
INFO No provenance attestation provenance

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

v1.4.2138

1 finding
INFO No provenance attestation provenance

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

v1.4.2137

1 finding
INFO No provenance attestation provenance

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

v1.4.2136

1 finding
INFO No provenance attestation provenance

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

v1.4.2135

1 finding
INFO No provenance attestation provenance

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

v1.4.2134

1 finding
INFO No provenance attestation provenance

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

v1.4.2133

1 finding
INFO No provenance attestation provenance

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

v1.4.2132

1 finding
INFO No provenance attestation provenance

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

v1.4.2131

1 finding
INFO No provenance attestation provenance

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

v1.4.2128

1 finding
INFO No provenance attestation provenance

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

v1.4.2127

1 finding
INFO No provenance attestation provenance

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

v1.4.2126

1 finding
INFO No provenance attestation provenance

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

v1.4.2125

1 finding
INFO No provenance attestation provenance

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

v1.4.2124

1 finding
INFO No provenance attestation provenance

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

v1.4.2123

1 finding
INFO No provenance attestation provenance

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

v1.4.2122

1 finding
INFO No provenance attestation provenance

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