← Home

@reltio/authoring

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
source-diff encoded-string-file:bundle.js AI (source-diff): Long encoded strings are webpack UMD bundle artifacts; consistent across all versions of this package. ai
provenance no-provenance AI (provenance): Org publishes 700+ versions without provenance; stable pattern for this package. ai
npm-metadata no-description AI (npm-metadata): Stable pattern across all versions of this internal package; not a risk signal here. ai
bogus-package bogus-package AI (bogus-package): Internal enterprise package; missing public metadata is expected for org-scoped private modules. ai
phantom-deps phantom-dep:@reltio/mdm-sdk AI (phantom-deps): Same-org scoped dep; phantom-dep heuristic unreliable for bundled packages with bundle.js as main. ai
phantom-deps phantom-dep:@reltio/mdm-module AI (phantom-deps): Same-org scoped dep; phantom-dep heuristic unreliable for bundled packages with bundle.js as main. ai
phantom-deps phantom-dep:@reltio/components AI (phantom-deps): Same-org scoped dep; phantom-dep heuristic unreliable for bundled packages with bundle.js as main. ai
phantom-deps phantom-dep:@reltio/profile AI (phantom-deps): Same-org scoped dep; phantom-dep heuristic unreliable for bundled packages with bundle.js as main. ai

Versions (showing 100 of 491)

Version Deps Published
1.4.2248 4 / 0
1.4.2247 4 / 0
1.4.2246 4 / 0
1.4.2245 4 / 0
1.4.2244 4 / 0
1.4.2243 4 / 0
1.4.2242 4 / 0
1.4.2241 4 / 0
1.4.2240 4 / 0
1.4.2239 4 / 0
1.4.2238 4 / 0
1.4.2237 4 / 0
1.4.2236 4 / 0
1.4.2235 4 / 0
1.4.2234 4 / 0
1.4.2233 4 / 0
1.4.2232 4 / 0
1.4.2231 4 / 0
1.4.2230 4 / 0
1.4.2229 4 / 0
1.4.2228 4 / 0
1.4.2227 4 / 0
1.4.2226 4 / 0
1.4.2225 4 / 0
1.4.2224 4 / 0
1.4.2223 4 / 0
1.4.2222 4 / 0
1.4.2221 4 / 0
1.4.2220 4 / 0
1.4.2219 4 / 0
1.4.2218 4 / 0
1.4.2217 4 / 0
1.4.2216 4 / 0
1.4.2215 4 / 0
1.4.2214 4 / 0
1.4.2213 4 / 0
1.4.2212 4 / 0
1.4.2211 4 / 0
1.4.2210 4 / 0
1.4.2209 4 / 0
1.4.2208 4 / 0
1.4.2207 4 / 0
1.4.2206 4 / 0
1.4.2205 4 / 0
1.4.2204 4 / 0
1.4.2203 4 / 0
1.4.2202 4 / 0
1.4.2201 4 / 0
1.4.2200 4 / 0
1.4.2199 4 / 0
1.4.2198 4 / 0
1.4.2197 4 / 0
1.4.2196 4 / 0
1.4.2195 4 / 0
1.4.2194 4 / 0
1.4.2193 4 / 0
1.4.2192 4 / 0
1.4.2191 4 / 0
1.4.2190 4 / 0
1.4.2189 4 / 0
1.4.2188 4 / 0
1.4.2187 4 / 0
1.4.2186 4 / 0
1.4.2185 4 / 0
1.4.2184 4 / 0
1.4.2183 4 / 0
1.4.2182 4 / 0
1.4.2181 4 / 0
1.4.2180 4 / 0
1.4.2179 4 / 0
1.4.2178 4 / 0
1.4.2177 4 / 0
1.4.2176 4 / 0
1.4.2175 4 / 0
1.4.2174 4 / 0
1.4.2173 4 / 0
1.4.2172 4 / 0
1.4.2171 4 / 0
1.4.2170 4 / 0
1.4.2169 4 / 0
1.4.2168 4 / 0
1.4.2167 4 / 0
1.4.2166 4 / 0
1.4.2165 4 / 0
1.4.2164 4 / 0
1.4.2163 4 / 0
1.4.2162 4 / 0
1.4.2161 4 / 0
1.4.2160 4 / 0
1.4.2159 4 / 0
1.4.2158 4 / 0
1.4.2157 4 / 0
1.4.2156 4 / 0
1.4.2153 4 / 0
1.4.2152 4 / 0
1.4.2151 4 / 0
1.4.2150 4 / 0
1.4.2149 4 / 0
1.4.2148 4 / 0
1.4.2147 4 / 0
Showing 100 of 491 Next page →

v1.4.2178

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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