@everymatrix/player-account-self-exclusion
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:components/PlayerAccountGeneralConfirmationModal-DeXn4IWi.cjs | AI (source-diff): Minified Svelte component bundle output; stable pattern for this package. | ai | |
| source-diff | net-exec-file:components/PlayerAccountSelfExclusion-u8FQDAXD.js | AI (source-diff): Svelte runtime uses fetch + dynamic patterns; not malicious. | ai | |
| source-diff | net-exec-file:components/PlayerAccountSelfExclusion-Bo9o9nYS.js | AI (source-diff): Svelte runtime uses fetch + dynamic patterns; not malicious. | ai | |
| source-diff | net-exec-file:components/PlayerAccountSelfExclusion-CoDh2WOg.cjs | AI (source-diff): Svelte runtime uses fetch + dynamic patterns; not malicious. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountSelfExclusion-u8FQDAXD.js | AI (source-diff): Minified Svelte component bundle output; stable pattern for this package. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountSelfExclusion-Bo9o9nYS.js | AI (source-diff): Minified Svelte component bundle output; stable pattern for this package. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGeneralConfirmationModal-CshJ-jjp.js | AI (source-diff): Minified Svelte component bundle output; stable pattern for this package. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGeneralConfirmationModal-CKTjGwYF.js | AI (source-diff): Minified Svelte component bundle output; stable pattern for this package. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountSelfExclusion-CoDh2WOg.cjs | AI (source-diff): Minified Svelte component bundle output; stable pattern for this package. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountModal-CWfuV1IK.cjs | AI (source-diff): Minified Svelte component bundle output; stable pattern for this package. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGeneralConfirmationModal-DMzxz7tw.js | AI (source-diff): Standard minified component chunk from Vite build pipeline. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountSelfExclusion-DXYdyTDz.js | AI (source-diff): Standard Vite/Rollup minified bundle output; hash-suffixed filenames are content-addressed chunks. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountSelfExclusion-WADwqQOF.js | AI (source-diff): Standard Vite/Rollup minified bundle output; hash-suffixed filenames are content-addressed chunks. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGeneralConfirmationModal-DqdxuF-H.js | AI (source-diff): Standard minified component chunk from Vite build pipeline. | ai | |
| source-diff | net-exec-file:components/PlayerAccountSelfExclusion-DXYdyTDz.js | AI (source-diff): Network calls and dynamic execution are part of the Svelte/Stencil component runtime, not dropper behavior. | ai | |
| source-diff | net-exec-file:components/PlayerAccountSelfExclusion-WADwqQOF.js | AI (source-diff): Network calls and dynamic execution are part of the Svelte/Stencil component runtime, not dropper behavior. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountModal-B0Gpvs7c.cjs | AI (source-diff): Standard minified Svelte/Rollup build output for this org's component packages. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountSelfExclusion-B1KxL7Uc.cjs | AI (source-diff): Standard minified Svelte/Rollup build output for this org's component packages. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGeneralConfirmationModal-DXxiPGY9.cjs | AI (source-diff): Standard minified Svelte/Rollup build output for this org's component packages. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountSelfExclusion-DJSl2b5x.js | AI (source-diff): Standard minified Svelte/Rollup build output for this org's component packages. | ai | |
| source-diff | net-exec-file:components/PlayerAccountSelfExclusion-C-gMfNgb.js | AI (source-diff): Network calls are fetch/XHR for API data; dynamic execution is Svelte runtime Promise handling — not dropper behavior. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountSelfExclusion-C-gMfNgb.js | AI (source-diff): Standard minified Svelte/Rollup build output for this org's component packages. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGeneralConfirmationModal-gcAOCwXn.js | AI (source-diff): Standard minified Svelte/Rollup build output for this org's component packages. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGeneralConfirmationModal-D8akNs65.js | AI (source-diff): Standard minified Svelte/Rollup build output for this org's component packages. | ai | |
| source-diff | net-exec-file:components/PlayerAccountSelfExclusion-DJSl2b5x.js | AI (source-diff): Network calls are fetch/XHR for API data; dynamic execution is Svelte runtime Promise handling — not dropper behavior. | ai | |
| source-diff | net-exec-file:components/PlayerAccountSelfExclusion-B1KxL7Uc.cjs | AI (source-diff): Network calls are fetch/XHR for API data; dynamic execution is Svelte runtime Promise handling — not dropper behavior. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped component library with 861 versions; missing metadata fields are a consistent pattern, not spam indicators. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): Fires inside vaadin-development-mode-detector, a known third-party utility; stable false positive for this package. | ai |
Versions (showing 100 of 212)
| Version | Deps | Published |
|---|---|---|
| 1.83.0 | 0 / 0 | |
| 1.82.0 | 0 / 0 | |
| 1.81.2 | 0 / 0 | |
| 1.81.1 | 0 / 0 | |
| 1.81.0 | 0 / 0 | |
| 1.80.19 | 0 / 0 | |
| 1.80.18 | 0 / 0 | |
| 1.80.17 | 0 / 0 | |
| 1.80.16 | 0 / 0 | |
| 1.80.15 | 0 / 0 | |
| 1.80.14 | 0 / 0 | |
| 1.80.13 | 0 / 0 | |
| 1.80.12 | 0 / 0 | |
| 1.80.11 | 0 / 0 | |
| 1.80.10 | 0 / 0 | |
| 1.80.9 | 0 / 0 | |
| 1.80.8 | 0 / 0 | |
| 1.80.7 | 0 / 0 | |
| 1.80.6 | 0 / 0 | |
| 1.80.5 | 0 / 0 | |
| 1.80.4 | 0 / 0 | |
| 1.80.3 | 0 / 0 | |
| 1.80.2 | 0 / 0 | |
| 1.80.1 | 0 / 0 | |
| 1.80.0 | 0 / 0 | |
| 1.77.32 | 0 / 0 | |
| 1.77.31 | 0 / 0 | |
| 1.77.30 | 0 / 0 | |
| 1.77.29 | 0 / 0 | |
| 1.77.28 | 0 / 0 | |
| 1.77.27 | 0 / 0 | |
| 1.77.26 | 0 / 0 | |
| 1.77.25 | 0 / 0 | |
| 1.77.24 | 0 / 0 | |
| 1.77.23 | 0 / 0 | |
| 1.77.22 | 0 / 0 | |
| 1.77.21 | 0 / 0 | |
| 1.77.20 | 0 / 0 | |
| 1.77.19 | 0 / 0 | |
| 1.77.18 | 0 / 0 | |
| 1.77.17 | 0 / 0 | |
| 1.77.16 | 0 / 0 | |
| 1.77.15 | 0 / 0 | |
| 1.77.14 | 0 / 0 | |
| 1.77.13 | 0 / 0 | |
| 1.77.12 | 0 / 0 | |
| 1.77.11 | 0 / 0 | |
| 1.77.10 | 0 / 0 | |
| 1.77.9 | 0 / 0 | |
| 1.77.8 | 0 / 0 | |
| 1.77.7 | 0 / 0 | |
| 1.77.6 | 0 / 0 | |
| 1.77.5 | 0 / 0 | |
| 1.77.4 | 0 / 0 | |
| 1.77.3 | 0 / 0 | |
| 1.77.2 | 0 / 0 | |
| 1.77.1 | 0 / 0 | |
| 1.77.0 | 0 / 0 | |
| 1.76.14 | 0 / 0 | |
| 1.76.13 | 0 / 0 | |
| 1.76.12 | 0 / 0 | |
| 1.76.11 | 0 / 0 | |
| 1.76.10 | 0 / 0 | |
| 1.76.9 | 0 / 0 | |
| 1.76.8 | 0 / 0 | |
| 1.76.7 | 0 / 0 | |
| 1.76.6 | 0 / 0 | |
| 1.76.5 | 0 / 0 | |
| 1.76.4 | 0 / 0 | |
| 1.76.3 | 0 / 0 | |
| 1.76.1 | 0 / 0 | |
| 1.76.0 | 0 / 0 | |
| 1.75.1 | 0 / 0 | |
| 1.75.0 | 0 / 0 | |
| 1.74.10 | 0 / 0 | |
| 1.74.8 | 0 / 0 | |
| 1.74.7 | 0 / 0 | |
| 1.74.6 | 0 / 0 | |
| 1.74.5 | 0 / 0 | |
| 1.74.4 | 0 / 0 | |
| 1.74.3 | 0 / 0 | |
| 1.74.2 | 0 / 0 | |
| 1.74.1 | 0 / 0 | |
| 1.74.0 | 0 / 0 | |
| 1.73.2 | 0 / 0 | |
| 1.73.1 | 0 / 0 | |
| 1.73.0 | 0 / 0 | |
| 1.72.2 | 0 / 0 | |
| 1.72.1 | 0 / 0 | |
| 1.72.0 | 0 / 0 | |
| 1.71.1 | 0 / 0 | |
| 1.71.0 | 0 / 0 | |
| 1.70.1 | 0 / 0 | |
| 1.70.0 | 0 / 0 | |
| 1.69.3 | 0 / 0 | |
| 1.69.2 | 0 / 0 | |
| 1.69.0 | 0 / 0 | |
| 1.68.0 | 0 / 0 | |
| 1.67.3 | 0 / 0 | |
| 1.67.0 | 0 / 0 |
v1.83.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.82.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.81.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.81.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.81.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.80.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.80.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.80.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.80.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.80.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.80.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.80.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.80.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.80.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.80.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.80.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.80.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.80.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.80.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.80.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.80.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.80.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.80.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.76.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.76.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.76.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.76.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.76.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.76.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.76.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.76.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.76.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.76.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.76.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.76.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.76.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.75.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.75.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.74.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.74.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.74.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.74.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.74.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.74.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.74.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.74.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.74.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.73.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.73.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.73.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.72.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.72.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.72.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.71.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.71.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.70.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.70.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.69.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.69.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.69.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.68.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.67.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.67.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.