@everymatrix/player-account-gaming-limits-group-edit
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/PlayerAccountGamingLimitsGroupEdit-CN09QvR3.js | AI (source-diff): Standard Svelte/Vite minified build output; i18n and component logic clearly readable. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsPopup-CYNiCT4V.cjs | AI (source-diff): Standard Svelte/Vite minified build output; readable i18n and component code. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountModal-4fKW33kt.cjs | AI (source-diff): Standard Svelte/Vite minified build output; modal component logic clearly readable. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsConfirmationModal-Bg8Q2dBa.js | AI (source-diff): Standard Svelte/Vite minified build output; Svelte runtime internals, not malicious. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsConfirmationModal-DLTfnyHJ.js | AI (source-diff): Standard Svelte/Vite minified build output; Svelte runtime internals, not malicious. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsGroupEdit-BCX8sKN5.js | AI (source-diff): Standard Svelte/Vite minified build output; i18n and component logic clearly readable. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsConfirmationModal-BQRpJqej.cjs | AI (source-diff): Standard Svelte/Vite minified build output; readable runtime and component code, not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsGroupEdit-0kwlLjjE.cjs | AI (source-diff): Standard Svelte/Vite minified build output; i18n strings and component logic visible, not malicious. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsGroupEdit-BiY0JFzY.js | AI (source-diff): Standard minified Svelte/JS bundle output; consistent with this package's established build pattern across 882 versions. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsGroupEdit-H_QSbujT.js | AI (source-diff): Standard minified Svelte/JS bundle output; consistent with this package's established build pattern across 882 versions. | ai | |
| npm-metadata | no-description | AI (npm-metadata): No description is a stable pattern for this scoped component package family. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is a stable pattern across this package's version history. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped component library; sparse metadata is consistent across all 882 versions of this package family. | ai |
Versions (showing 8 of 208)
| Version | Deps | Published |
|---|---|---|
| 1.69.0 | 0 / 0 | |
| 1.68.0 | 0 / 0 | |
| 1.67.3 | 0 / 0 | |
| 1.67.0 | 0 / 0 | |
| 1.66.2 | 0 / 0 | |
| 1.66.1 | 0 / 0 | |
| 1.66.0 | 0 / 0 | |
| 1.65.3 | 0 / 0 |
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.
v1.66.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.66.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.66.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.65.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.