@reltio/profile
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 |
|---|---|---|---|---|
| source-diff | encoded-string-file:bundle.js | AI (source-diff): Standard webpack/UMD bundle output; long encoded strings are base64-encoded source maps or icon data, not malicious payloads. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent pattern across this org's packages; not a malware signal. | ai | |
| phantom-deps | phantom-dep:@reltio/mdm-sdk | AI (phantom-deps): Same org scope; likely re-exported or used indirectly via bundled output. | ai | |
| phantom-deps | phantom-dep:@reltio/mdm-module | AI (phantom-deps): Same org scope; likely re-exported or used indirectly via bundled output. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal enterprise package; missing metadata is expected for org-scoped private packages with 1842+ versions. | ai | |
| phantom-deps | phantom-dep:@reltio/interactions | AI (phantom-deps): Same org scope; likely re-exported or used indirectly via bundled output. | ai | |
| phantom-deps | phantom-dep:html2canvas | AI (phantom-deps): Referenced in config files; stable false positive for this bundled package. | ai | |
| phantom-deps | phantom-dep:object-hash | AI (phantom-deps): Referenced in config files; stable false positive for this bundled package. | ai | |
| phantom-deps | phantom-dep:@reltio/components | AI (phantom-deps): Same org scope; likely re-exported or used indirectly via bundled output. | ai |
Versions (showing 58 of 159)
| Version | Deps | Published |
|---|---|---|
| 1.4.2230 | 6 / 0 | |
| 1.4.2229 | 6 / 0 | |
| 1.4.2228 | 6 / 0 | |
| 1.4.2227 | 6 / 0 | |
| 1.4.2226 | 6 / 0 | |
| 1.4.2225 | 6 / 0 | |
| 1.4.2224 | 6 / 0 | |
| 1.4.2223 | 6 / 0 | |
| 1.4.2222 | 6 / 0 | |
| 1.4.2221 | 6 / 0 | |
| 1.4.2220 | 6 / 0 | |
| 1.4.2219 | 6 / 0 | |
| 1.4.2218 | 6 / 0 | |
| 1.4.2217 | 6 / 0 | |
| 1.4.2216 | 6 / 0 | |
| 1.4.2215 | 6 / 0 | |
| 1.4.2214 | 6 / 0 | |
| 1.4.2213 | 6 / 0 | |
| 1.4.2212 | 6 / 0 | |
| 1.4.2211 | 6 / 0 | |
| 1.4.2210 | 6 / 0 | |
| 1.4.2209 | 6 / 0 | |
| 1.4.2208 | 6 / 0 | |
| 1.4.2207 | 6 / 0 | |
| 1.4.2206 | 6 / 0 | |
| 1.4.2205 | 6 / 0 | |
| 1.4.2204 | 6 / 0 | |
| 1.4.2203 | 6 / 0 | |
| 1.4.2202 | 6 / 0 | |
| 1.4.2201 | 6 / 0 | |
| 1.4.2200 | 6 / 0 | |
| 1.4.2199 | 6 / 0 | |
| 1.4.2198 | 6 / 0 | |
| 1.4.2197 | 6 / 0 | |
| 1.4.2196 | 6 / 0 | |
| 1.4.2195 | 6 / 0 | |
| 1.4.2194 | 6 / 0 | |
| 1.4.2193 | 6 / 0 | |
| 1.4.2192 | 6 / 0 | |
| 1.4.2191 | 6 / 0 | |
| 1.4.2190 | 6 / 0 | |
| 1.4.2189 | 6 / 0 | |
| 1.4.2188 | 6 / 0 | |
| 1.4.2187 | 6 / 0 | |
| 1.4.2186 | 6 / 0 | |
| 1.4.2185 | 6 / 0 | |
| 1.4.2184 | 6 / 0 | |
| 1.4.2183 | 6 / 0 | |
| 1.4.2182 | 6 / 0 | |
| 1.4.2181 | 6 / 0 | |
| 1.4.2180 | 6 / 0 | |
| 1.4.2179 | 6 / 0 | |
| 1.4.2178 | 6 / 0 | |
| 1.4.2177 | 6 / 0 | |
| 1.4.2176 | 6 / 0 | |
| 1.4.2175 | 6 / 0 | |
| 1.4.2174 | 6 / 0 | |
| 1.4.2173 | 6 / 0 |
v1.4.2230
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2229
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2228
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2227
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2226
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2225
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2224
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2223
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2222
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2221
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2220
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2219
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2218
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2217
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2216
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2215
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2214
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2213
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2212
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2211
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2210
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2209
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2208
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2207
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2206
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2205
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2204
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2203
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2202
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2201
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2200
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2199
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2198
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2197
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2196
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2195
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2194
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2193
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2192
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2191
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2190
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2189
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2188
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2187
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2186
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2185
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2184
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2183
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2182
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2181
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2180
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2179
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2178
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2177
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2176
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2175
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2174
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2173
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.