@everymatrix/general-player-register-form
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/GeneralPlayerRegisterForm-Juj7dcCL.cjs | AI (source-diff): Standard bundled Svelte component output, not obfuscation. Stable for this package. | ai | |
| source-diff | obfuscated-file:components/GeneralPlayerRegisterFormStep3-kxkTfs8b.js | AI (source-diff): Bundled ESM output; not obfuscated. | ai | |
| source-diff | obfuscated-file:components/GeneralPlayerRegisterFormStep3-_1IX6ALN.js | AI (source-diff): Bundled ESM output; not obfuscated. | ai | |
| source-diff | obfuscated-file:components/GeneralPlayerRegisterFormStep2-ibhZJuL5.js | AI (source-diff): Bundled ESM output; not obfuscated. | ai | |
| source-diff | obfuscated-file:components/GeneralPlayerRegisterFormStep2-DCtPCA-O.js | AI (source-diff): Bundled ESM output; not obfuscated. | ai | |
| source-diff | obfuscated-file:components/GeneralPlayerRegisterFormStep1-DdQw5Sxj.js | AI (source-diff): Bundled ESM output; not obfuscated. | ai | |
| source-diff | obfuscated-file:components/GeneralPlayerRegisterFormStep1-CcUG3PlY.js | AI (source-diff): Bundled ESM with i18n strings; not obfuscated. | ai | |
| source-diff | obfuscated-file:components/GeneralPlayerRegisterForm-DkUp5-ze.js | AI (source-diff): Bundled ESM output; not obfuscated. | ai | |
| source-diff | obfuscated-file:components/GeneralPlayerRegisterForm-BnRgZ7r2.js | AI (source-diff): Bundled ESM Svelte component output; not obfuscated. | ai | |
| source-diff | obfuscated-file:components/GeneralPlayerSmsVerificationForm-B7vz32rX.cjs | AI (source-diff): Bundled CJS output with i18n strings; not obfuscated. | ai | |
| source-diff | obfuscated-file:components/GeneralPlayerRegisterFormStep3-DUT5mJja.cjs | AI (source-diff): Bundled CJS output with i18n strings; not obfuscated. | ai | |
| source-diff | obfuscated-file:components/GeneralPlayerRegisterFormStep2-CtVt3PB-.cjs | AI (source-diff): Bundled CJS with date-fns utilities; not obfuscated. | ai | |
| source-diff | obfuscated-file:components/GeneralPlayerRegisterFormStep1-9xba4-kD.cjs | AI (source-diff): Bundled CJS output with i18n strings; not obfuscated. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped internal component package; no repo/deps/keywords is normal for pre-built artifact distribution. | ai | |
| source-diff | obfuscated-file:components/GeneralPlayerRegisterFormStep1-CMPZi1JN.js | AI (source-diff): Standard Vite/Rollup minified bundle output; no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/GeneralPlayerRegisterForm-B_X7fQIv.js | AI (source-diff): Standard Vite/Rollup minified bundle output; no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/GeneralPlayerRegisterForm-CSiLhECi.js | AI (source-diff): Standard Vite/Rollup minified bundle output; no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/GeneralPlayerRegisterFormStep1-BMHYgnfZ.js | AI (source-diff): Standard Vite/Rollup minified bundle output; no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/GeneralPlayerRegisterFormStep2-B3140fSG.js | AI (source-diff): Standard Vite/Rollup minified bundle output; no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/GeneralPlayerRegisterFormStep2-Cqgu7ded.js | AI (source-diff): Standard Vite/Rollup minified bundle output; no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/GeneralPlayerRegisterFormStep3-BZ6euAod.js | AI (source-diff): Standard Vite/Rollup minified bundle output; no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/GeneralPlayerRegisterFormStep3-CV_cw6BQ.js | AI (source-diff): Standard Vite/Rollup minified bundle output; no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/GeneralPlayerRegisterFormStep1-wGHSOnwh.cjs | AI (source-diff): Standard Rollup/Vite minified bundle output for this component library. | ai | |
| source-diff | obfuscated-file:components/GeneralPlayerRegisterFormStep3-npTlDfFM.js | AI (source-diff): Standard Rollup/Vite minified bundle output for this component library. | ai | |
| source-diff | obfuscated-file:components/GeneralPlayerRegisterFormStep3-D-Y-mrlN.js | AI (source-diff): Standard Rollup/Vite minified bundle output for this component library. | ai | |
| source-diff | obfuscated-file:components/GeneralPlayerRegisterFormStep2-Vec1P-dd.js | AI (source-diff): Standard Rollup/Vite minified bundle output for this component library. | ai | |
| source-diff | obfuscated-file:components/GeneralPlayerRegisterFormStep2-1OYQs6qJ.js | AI (source-diff): Standard Rollup/Vite minified bundle output for this component library. | ai | |
| source-diff | obfuscated-file:components/GeneralPlayerRegisterFormStep1-Dz4Wqs3b.js | AI (source-diff): Standard Rollup/Vite minified bundle output for this component library. | ai | |
| source-diff | obfuscated-file:components/GeneralPlayerRegisterFormStep1-CTy5kzLO.js | AI (source-diff): Standard Rollup/Vite minified bundle output for this component library. | ai | |
| source-diff | obfuscated-file:components/GeneralPlayerRegisterForm-h28HFvAY.js | AI (source-diff): Standard Rollup/Vite minified bundle output for this component library. | ai | |
| source-diff | obfuscated-file:components/GeneralPlayerRegisterForm-BRfuwsmL.js | AI (source-diff): Standard Rollup/Vite minified bundle output for this component library. | ai | |
| source-diff | obfuscated-file:components/GeneralPlayerSmsVerificationForm-CjmEVjGS.cjs | AI (source-diff): Standard Rollup/Vite minified bundle output for this component library. | ai | |
| source-diff | obfuscated-file:components/GeneralPlayerRegisterForm-JRkRI6tq.cjs | AI (source-diff): Standard Rollup/Vite minified bundle output for this component library; not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:components/GeneralPlayerRegisterFormStep3-0YZf9qtI.cjs | AI (source-diff): Standard Rollup/Vite minified bundle output for this component library. | ai | |
| source-diff | obfuscated-file:components/GeneralPlayerRegisterFormStep2-DSEY56Dl.cjs | AI (source-diff): Standard Rollup/Vite minified bundle output for this component library. | ai | |
| provenance | publisher-changed | AI (provenance): adrian.pripon is an established org publisher (11669 approved); transition from emfe_release appears to be an internal account change. | ai |
Versions (showing 51 of 260)
| Version | Deps | Published |
|---|---|---|
| 1.94.29 | 0 / 0 | |
| 1.94.28 | 0 / 0 | |
| 1.94.27 | 0 / 0 | |
| 1.94.26 | 0 / 0 | |
| 1.94.25 | 0 / 0 | |
| 1.94.24 | 0 / 0 | |
| 1.94.23 | 0 / 0 | |
| 1.94.22 | 0 / 0 | |
| 1.94.21 | 0 / 0 | |
| 1.94.19 | 0 / 0 | |
| 1.94.18 | 0 / 0 | |
| 1.94.17 | 0 / 0 | |
| 1.94.16 | 0 / 0 | |
| 1.94.15 | 0 / 0 | |
| 1.94.9 | 0 / 0 | |
| 1.94.8 | 0 / 0 | |
| 1.94.7 | 0 / 0 | |
| 1.94.6 | 0 / 0 | |
| 1.94.5 | 0 / 0 | |
| 1.94.4 | 0 / 0 | |
| 1.94.3 | 0 / 0 | |
| 1.94.2 | 0 / 0 | |
| 1.94.1 | 0 / 0 | |
| 1.94.0 | 0 / 0 | |
| 1.93.15 | 0 / 0 | |
| 1.93.14 | 0 / 0 | |
| 1.93.13 | 0 / 0 | |
| 1.93.12 | 0 / 0 | |
| 1.93.11 | 0 / 0 | |
| 1.93.10 | 0 / 0 | |
| 1.93.9 | 0 / 0 | |
| 1.93.8 | 0 / 0 | |
| 1.93.7 | 0 / 0 | |
| 1.93.6 | 0 / 0 | |
| 1.93.5 | 0 / 0 | |
| 1.93.4 | 0 / 0 | |
| 1.93.3 | 0 / 0 | |
| 1.93.2 | 0 / 0 | |
| 1.93.1 | 0 / 0 | |
| 1.93.0 | 0 / 0 | |
| 1.92.8 | 0 / 0 | |
| 1.92.7 | 0 / 0 | |
| 1.92.6 | 0 / 0 | |
| 1.92.5 | 0 / 0 | |
| 1.92.4 | 0 / 0 | |
| 1.92.3 | 0 / 0 | |
| 1.92.2 | 0 / 0 | |
| 1.92.1 | 0 / 0 | |
| 1.92.0 | 0 / 0 | |
| 1.91.2 | 0 / 0 | |
| 1.91.1 | 0 / 0 |
v1.94.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.15
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (goe.suta) than the most recent previously approved version (adrian.pripon) on 2026-05-26, but goe.suta is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.94.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.8
9 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.7
9 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.6
9 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.5
9 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.93.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.93.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.93.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.93.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.93.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.93.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.93.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.93.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.93.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.93.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.93.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.93.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.93.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.93.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.92.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.92.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.92.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.92.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.92.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.92.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.92.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.92.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.91.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.91.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.