@everymatrix/bonus-elevate-shop
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@everymatrix/general-input | AI (phantom-deps): Internal org dependency; likely re-exported or used transitively in monorepo. | ai | |
| phantom-deps | phantom-dep:@everymatrix/general-animation-loading | AI (phantom-deps): Internal org dependency; likely re-exported or used transitively in monorepo. | ai | |
| phantom-deps | phantom-dep:@everymatrix/general-styling-wrapper | AI (phantom-deps): Internal org dependency; likely re-exported or used transitively in monorepo. | ai | |
| phantom-deps | phantom-dep:@everymatrix/bonus-pagination-nav | AI (phantom-deps): Internal org dependency; likely re-exported or used transitively in monorepo. | ai | |
| phantom-deps | phantom-dep:@everymatrix/player-elevate-card | AI (phantom-deps): Internal org dependency; likely re-exported or used transitively in monorepo. | ai | |
| source-diff | obfuscated-file:dist/bonus-elevate-shop/player-elevate-card-items-1afa5433.js | AI (source-diff): Bundled date-fns/component code, minified not obfuscated. | ai | |
| source-diff | obfuscated-file:dist/bonus-elevate-shop/bonus-elevate-shop_6.entry.js | AI (source-diff): Stencil/rollup minified bundle output, not true obfuscation. | ai | |
| source-diff | obfuscated-file:dist/bonus-elevate-shop/index-19906d91.js | AI (source-diff): Minified Stencil runtime, not true obfuscation. | ai | |
| source-diff | obfuscated-file:dist/cjs/bonus-elevate-shop_6.cjs.entry.js | AI (source-diff): CJS build output mirrors ESM, standard bundler artifact. | ai | |
| source-diff | obfuscated-file:dist/esm/bonus-elevate-shop_6.entry.js | AI (source-diff): ESM bundler output, no malicious behavior found. | ai | |
| source-diff | obfuscated-file:dist/bonus-elevate-shop/player-elevate-card-items-818d80d1.js | AI (source-diff): Bundled minified vendor code (date-fns), not obfuscation; consistent with prior builds. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Internal component library package, consistently sparse metadata across versions. | ai | |
| source-diff | obfuscated-file:dist/bonus-elevate-shop/player-elevate-card-items-3e027a1b.js | AI (source-diff): Bundled minified build output (esm/cjs chunk), not true obfuscation. | ai | |
| source-diff | obfuscated-file:dist/bonus-elevate-shop/locale.utils-10bf5b6c.js | AI (source-diff): Minified locale/utility bundle; content is plaintext i18n strings and date-fns helpers, not obfuscated malware. | ai | |
| source-diff | obfuscated-file:dist/bonus-elevate-shop/player-elevate-card-items-b1417523.js | AI (source-diff): Minified component chunk; content is standard date-fns and UI logic, no suspicious network or exec patterns. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established @everymatrix org with 422 versions; sparse metadata is a consistent pattern for their internal component packages. | ai |
Versions (showing 100 of 512)
| Version | Deps | Published |
|---|---|---|
| 1.61.1 | 0 / 0 | |
| 1.61.0 | 0 / 0 | |
| 1.60.2 | 0 / 0 | |
| 1.60.1 | 0 / 0 | |
| 1.60.0 | 0 / 0 | |
| 1.59.3 | 0 / 0 | |
| 1.59.2 | 0 / 0 | |
| 1.59.1 | 0 / 0 | |
| 1.59.0 | 0 / 0 | |
| 1.58.5 | 0 / 0 | |
| 1.58.4 | 0 / 0 | |
| 1.58.3 | 0 / 0 | |
| 1.58.2 | 0 / 0 | |
| 1.58.0 | 0 / 0 | |
| 1.57.0 | 0 / 0 | |
| 1.56.3 | 0 / 0 | |
| 1.56.2 | 0 / 0 | |
| 1.56.0 | 0 / 0 | |
| 1.55.0 | 0 / 0 | |
| 1.54.12 | 0 / 0 | |
| 1.54.11 | 0 / 0 | |
| 1.54.10 | 0 / 0 | |
| 1.54.9 | 5 / 0 | |
| 1.54.8 | 5 / 0 | |
| 1.54.6 | 5 / 0 | |
| 1.54.4 | 5 / 0 | |
| 1.54.2 | 5 / 0 | |
| 1.54.0 | 5 / 0 | |
| 1.53.12 | 5 / 0 | |
| 1.53.11 | 5 / 0 | |
| 1.53.10 | 5 / 0 | |
| 1.53.0 | 5 / 0 | |
| 1.52.6 | 5 / 0 | |
| 1.52.5 | 5 / 0 | |
| 1.52.4 | 5 / 0 | |
| 1.52.3 | 5 / 0 | |
| 1.52.2 | 5 / 0 | |
| 1.52.1 | 5 / 0 | |
| 1.52.0 | 5 / 0 | |
| 1.51.0 | 5 / 0 | |
| 1.50.1 | 5 / 0 | |
| 1.50.0 | 5 / 0 | |
| 1.49.2 | 5 / 0 | |
| 1.49.1 | 5 / 0 | |
| 1.49.0 | 5 / 0 | |
| 1.48.2 | 5 / 0 | |
| 1.48.1 | 5 / 0 | |
| 1.48.0 | 5 / 0 | |
| 1.47.3 | 3 / 0 | |
| 1.47.2 | 3 / 0 | |
| 1.47.1 | 3 / 0 | |
| 1.47.0 | 3 / 0 | |
| 1.46.1 | 3 / 0 | |
| 1.46.0 | 3 / 0 | |
| 1.45.14 | 3 / 0 | |
| 1.45.13 | 4 / 0 | |
| 1.45.11 | 3 / 0 | |
| 1.45.10 | 3 / 0 | |
| 1.45.9 | 3 / 0 | |
| 1.45.8 | 3 / 0 | |
| 1.45.7 | 3 / 0 | |
| 1.45.5 | 3 / 0 | |
| 1.45.4 | 3 / 0 | |
| 1.45.3 | 3 / 0 | |
| 1.45.2 | 3 / 0 | |
| 1.45.0 | 3 / 0 | |
| 1.44.0 | 0 / 3 | |
| 1.43.4 | 0 / 3 | |
| 1.43.3 | 0 / 3 | |
| 1.43.2 | 0 / 3 | |
| 1.43.1 | 0 / 3 | |
| 1.43.0 | 0 / 3 | |
| 1.42.0 | 0 / 3 | |
| 1.41.0 | 0 / 3 | |
| 1.40.0 | 0 / 3 | |
| 1.39.3 | 0 / 3 | |
| 1.39.2 | 0 / 3 | |
| 1.39.1 | 0 / 3 | |
| 1.39.0 | 0 / 3 | |
| 1.38.0 | 0 / 3 | |
| 1.37.11 | 0 / 3 | |
| 1.37.10 | 0 / 3 | |
| 1.37.9 | 0 / 3 | |
| 1.37.8 | 0 / 3 | |
| 1.37.7 | 0 / 3 | |
| 1.37.6 | 0 / 3 | |
| 1.37.5 | 0 / 3 | |
| 1.37.4 | 0 / 3 | |
| 1.37.3 | 0 / 3 | |
| 1.37.2 | 0 / 3 | |
| 1.37.0 | 0 / 3 | |
| 1.36.1 | 0 / 3 | |
| 1.36.0 | 0 / 3 | |
| 1.35.0 | 0 / 3 | |
| 1.34.2 | 0 / 3 | |
| 1.34.0 | 0 / 3 | |
| 1.33.5 | 0 / 3 | |
| 1.33.4 | 0 / 3 | |
| 1.33.3 | 0 / 2 | |
| 1.33.2 | 0 / 2 |
v1.61.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.61.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.60.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.60.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.60.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.59.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.59.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.59.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.59.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.58.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.58.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.58.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.58.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.58.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.57.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.56.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.56.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.56.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.55.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.54.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.54.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.54.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.54.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.54.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.54.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.54.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.54.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.54.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.53.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.53.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.53.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.53.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.52.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.52.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.52.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.52.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.52.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.52.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.52.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.51.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.50.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.50.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.49.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.49.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.49.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.48.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.48.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.48.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.47.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.47.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.47.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.47.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.46.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.46.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.44.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.43.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.43.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.43.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.43.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.43.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.42.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.41.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.40.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.39.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.39.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.39.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.39.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.38.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.36.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.36.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.35.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.34.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.34.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.