@everymatrix/lottery-game-page
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 | net-exec-file:dist/lottery-game-page/general-multi-select_17.entry.js | AI (source-diff): CSS URL fetch for widget theming; same benign pattern as other build targets. | ai | |
| source-diff | obfuscated-file:dist/esm/general-multi-select_17.entry.js | AI (source-diff): Same Stencil.js ESM build output; minified but not obfuscated. | ai | |
| source-diff | net-exec-file:dist/esm/general-multi-select_17.entry.js | AI (source-diff): Same CSS theming fetch pattern; benign for this widget package. | ai | |
| source-diff | obfuscated-file:dist/lottery-game-page/general-multi-select_17.entry.js | AI (source-diff): Minified Stencil component bundle; consistent with existing package distribution format. | ai | |
| source-diff | obfuscated-file:dist/cjs/general-multi-select_17.cjs.entry.js | AI (source-diff): Standard Stencil.js minified build output for a UI widget; long lines are bundled component code, not obfuscation. | ai | |
| source-diff | net-exec-file:dist/cjs/general-multi-select_17.cjs.entry.js | AI (source-diff): Network call is a CSS URL fetch for client theming; no arbitrary code execution — innerHTML set to fetched stylesheet text only. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent across all @everymatrix component packages; not a malice indicator here. | ai | |
| provenance | no-provenance | AI (provenance): No provenance across the entire @everymatrix package family; stable false positive. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established @everymatrix org with 521 versions; sparse metadata is a CI publishing pattern, not spam. | ai |
Versions (showing 16 of 223)
| Version | Deps | Published |
|---|---|---|
| 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.66.2 | 0 / 0 | |
| 1.66.1 | 0 / 0 | |
| 1.66.0 | 0 / 0 | |
| 1.65.3 | 0 / 0 |
v1.72.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.
v1.72.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.
v1.72.0
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.71.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.
v1.71.0
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.70.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.
v1.70.0
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.69.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.69.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.
v1.69.0
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.68.0
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.67.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.66.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.
v1.66.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.
v1.66.0
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.65.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.