@everymatrix/player-pending-withdrawals
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:components/PlayerPendingWithdrawals-Bzqu6OLt.cjs | AI (source-diff): Standard Vite/Svelte minified build output; consistent pattern across all @everymatrix component releases. | ai | |
| source-diff | obfuscated-file:components/PlayerPendingWithdrawals-BjI9f9KO.js | AI (source-diff): Standard Vite/Svelte minified build output; consistent pattern across all @everymatrix component releases. | ai | |
| source-diff | obfuscated-file:components/PlayerPendingWithdrawals-C0ER7kwj.js | AI (source-diff): Standard Vite/Svelte minified build output; consistent pattern across all @everymatrix component releases. | ai | |
| provenance | no-provenance | AI (provenance): No provenance across all 840+ versions; internal release pipeline does not use Sigstore. | ai | |
| bogus-package | bogus-package | AI (bogus-package): @everymatrix component packages consistently lack descriptions, repos, and deps — this is a stable org-wide pattern. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Org-wide pattern for @everymatrix component packages; not a malice indicator here. | ai |
Versions (showing 4 of 404)
| Version | Deps | Published |
|---|---|---|
| 1.0.72 | 0 / 0 | |
| 1.0.71 | 0 / 0 | |
| 1.0.70 | 0 / 0 | |
| 1.0.69 | 0 / 0 |
v1.0.72
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.0.71
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.0.70
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.0.69
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.