@everymatrix/general-registration-multistep
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 | obfuscated-file:dist/esm/PlayerConsents-Duni8Aqx-dd7cf325.js | AI (source-diff): Standard Rollup/Svelte minified build output for this scoped package; not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/general-registration-multistep/PlayerConsents-Duni8Aqx-dd7cf325.js | AI (source-diff): Standard Rollup/Svelte minified build output for this scoped package; not obfuscation. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): EveryMatrix internal team addition; publisher has strong approval track record on this package family. | ai | |
| source-diff | obfuscated-file:dist/cjs/PlayerConsents-Duni8Aqx-1d0f4f21.js | AI (source-diff): Standard Rollup/Svelte minified build output for this scoped package; not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/cjs/PlayerConsents-Cng_xhf4-70bd07e0.js | AI (source-diff): Standard minified Svelte/Rollup chunk; readable patterns, no obfuscation or malicious indicators. | ai | |
| source-diff | obfuscated-file:dist/esm/PlayerConsents-Cng_xhf4-89a9b943.js | AI (source-diff): Standard minified Svelte/Rollup chunk; readable patterns, no obfuscation or malicious indicators. | ai | |
| source-diff | obfuscated-file:dist/general-registration-multistep/PlayerConsents-Cng_xhf4-89a9b943.js | AI (source-diff): Standard minified Svelte/Rollup chunk; readable patterns, no obfuscation or malicious indicators. | ai | |
| source-diff | obfuscated-file:dist/esm/PlayerConsents-BtzEjirY-52f88049.js | AI (source-diff): Standard minified Svelte ESM bundle; same build pipeline pattern. | ai | |
| source-diff | obfuscated-file:dist/cjs/PlayerConsents-BtzEjirY-0870c312.js | AI (source-diff): Standard minified Svelte bundle output; consistent with this package's build pipeline across all versions. | ai | |
| source-diff | obfuscated-file:dist/general-registration-multistep/PlayerConsents-BtzEjirY-52f88049.js | AI (source-diff): Standard minified Svelte bundle for unpkg/CDN distribution; same build pipeline pattern. | ai | |
| source-diff | obfuscated-file:dist/esm/PlayerConsents-C93YUnq0-2e7ff8d3.js | AI (source-diff): Standard minified Svelte build artifact; pattern is consistent across all versions of this component library. | ai | |
| source-diff | obfuscated-file:dist/cjs/PlayerConsents-C93YUnq0-af99ac14.js | AI (source-diff): Standard minified CJS Svelte build artifact; consistent with package's build pipeline. | ai | |
| source-diff | obfuscated-file:dist/general-registration-multistep/PlayerConsents-C93YUnq0-2e7ff8d3.js | AI (source-diff): Standard minified Svelte build artifact; same pattern as other dist outputs in this package. | ai | |
| source-diff | obfuscated-file:dist/general-registration-multistep/index-35614435.js | AI (source-diff): Stencil.js build output; minified bundle files are expected artifacts for this package across all versions. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Corporate scoped package with 122 versions; missing metadata is typical for internal widget libraries published via private registry. | ai | |
| provenance | no-provenance | AI (provenance): Internal corporate package published via JFrog Artifactory; provenance attestation not expected. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Stable pattern across this package's many versions; not a malware indicator. | ai |
Versions (showing 40 of 164)
| Version | Deps | Published |
|---|---|---|
| 1.87.40 | 0 / 0 | |
| 1.87.39 | 0 / 0 | |
| 1.87.38 | 0 / 0 | |
| 1.87.37 | 0 / 0 | |
| 1.87.36 | 0 / 0 | |
| 1.87.35 | 0 / 0 | |
| 1.87.34 | 0 / 0 | |
| 1.87.33 | 0 / 0 | |
| 1.87.32 | 0 / 0 | |
| 1.87.31 | 0 / 0 | |
| 1.87.30 | 0 / 0 | |
| 1.87.29 | 0 / 0 | |
| 1.87.28 | 0 / 0 | |
| 1.87.27 | 0 / 0 | |
| 1.87.26 | 0 / 0 | |
| 1.87.25 | 0 / 0 | |
| 1.87.24 | 0 / 0 | |
| 1.87.23 | 0 / 0 | |
| 1.87.22 | 0 / 0 | |
| 1.87.21 | 0 / 0 | |
| 1.87.20 | 0 / 0 | |
| 1.87.19 | 0 / 0 | |
| 1.87.18 | 0 / 0 | |
| 1.87.17 | 0 / 0 | |
| 1.87.16 | 0 / 0 | |
| 1.87.15 | 0 / 0 | |
| 1.87.14 | 0 / 0 | |
| 1.87.13 | 0 / 0 | |
| 1.87.12 | 0 / 0 | |
| 1.87.11 | 0 / 0 | |
| 1.87.10 | 0 / 0 | |
| 1.87.9 | 0 / 0 | |
| 1.87.8 | 0 / 0 | |
| 1.87.7 | 0 / 0 | |
| 1.87.6 | 0 / 0 | |
| 1.87.5 | 0 / 0 | |
| 1.87.4 | 0 / 0 | |
| 1.87.3 | 0 / 0 | |
| 1.87.2 | 0 / 0 | |
| 0.0.1 | 0 / 0 |
v1.87.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.87.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.87.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.87.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.87.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.87.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.87.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.87.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.87.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.87.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.87.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.87.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.87.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.87.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.87.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.87.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.87.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.87.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.87.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.87.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.87.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.87.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.87.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.87.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.87.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.87.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.87.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.87.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.87.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.87.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.87.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.87.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.87.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.87.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.87.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.87.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.87.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.87.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.