@everymatrix/player-elevate-points-history
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/player-elevate-card | AI (phantom-deps): Same-org internal dependency; likely used transitively or in collection exports. | ai | |
| phantom-deps | phantom-dep:@everymatrix/general-animation-loading | AI (phantom-deps): Same-org internal dependency; likely used transitively or in collection exports. | ai | |
| phantom-deps | phantom-dep:@everymatrix/general-styling-wrapper | AI (phantom-deps): Same-org internal dependency; likely used transitively or in collection exports. | ai | |
| phantom-deps | phantom-dep:@everymatrix/bonus-pagination-limits | AI (phantom-deps): Same-org internal dependency; likely used transitively or in collection exports. | ai | |
| phantom-deps | phantom-dep:@everymatrix/bonus-pagination-nav | AI (phantom-deps): Same-org internal dependency; likely used transitively or in collection exports. | ai | |
| source-diff | obfuscated-file:dist/esm/bonus-pagination-limits_7.entry.js | AI (source-diff): Bundled Stencil output, not true obfuscation. | ai | |
| source-diff | obfuscated-file:dist/cjs/bonus-pagination-limits_7.cjs.entry.js | AI (source-diff): Bundled Stencil output, not true obfuscation; readable component code. | ai | |
| source-diff | obfuscated-file:dist/player-elevate-points-history/bonus-pagination-limits_7.entry.js | AI (source-diff): Minified bundle, not obfuscated; matches build pipeline. | ai | |
| source-diff | obfuscated-file:dist/player-elevate-points-history/index-717e7bf3.js | AI (source-diff): Minified Stencil runtime, not obfuscated. | ai | |
| source-diff | obfuscated-file:dist/player-elevate-points-history/player-elevate-card-items-f1914b1a.js | AI (source-diff): Minified date-fns/component bundle, not obfuscated. | ai | |
| source-diff | obfuscated-file:dist/player-elevate-points-history/player-elevate-card-items-7775401c.js | AI (source-diff): Minified bundled library code (date-fns/Stencil), not obfuscation; no malicious behavior. | ai | |
| source-diff | obfuscated-file:dist/player-elevate-points-history/player-elevate-card-items-5a57ffb1.js | AI (source-diff): Bundled minified date-fns/util code, not true obfuscation. | ai | |
| source-diff | obfuscated-file:dist/player-elevate-points-history/player-elevate-card-items-7ee425c6.js | AI (source-diff): Minified component bundle with date-fns utilities; standard build artifact for this package. | ai | |
| source-diff | obfuscated-file:dist/player-elevate-points-history/locale.utils-10bf5b6c.js | AI (source-diff): Minified locale string bundle; no obfuscation or malicious content — stable pattern for this package. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent with @everymatrix org publishing pattern across many versions. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is common; no other risk signals present. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Large @everymatrix org with 416 versions; sparse metadata is a consistent pattern for internal scoped components, not spam. | ai |
Versions (showing 51 of 458)
| Version | Deps | Published |
|---|---|---|
| 1.94.81 | 0 / 0 | |
| 1.94.80 | 0 / 0 | |
| 1.94.79 | 0 / 0 | |
| 1.94.78 | 0 / 0 | |
| 1.94.77 | 0 / 0 | |
| 1.94.76 | 0 / 0 | |
| 1.94.75 | 0 / 0 | |
| 1.94.74 | 0 / 0 | |
| 1.94.73 | 0 / 0 | |
| 1.94.72 | 0 / 0 | |
| 1.94.71 | 0 / 0 | |
| 1.94.70 | 0 / 0 | |
| 1.94.69 | 0 / 0 | |
| 1.94.68 | 0 / 0 | |
| 1.94.67 | 0 / 0 | |
| 1.94.66 | 0 / 0 | |
| 1.94.65 | 0 / 0 | |
| 1.94.64 | 0 / 0 | |
| 1.94.63 | 0 / 0 | |
| 1.94.62 | 0 / 0 | |
| 1.94.61 | 0 / 0 | |
| 1.94.60 | 0 / 0 | |
| 1.94.59 | 0 / 0 | |
| 1.94.58 | 0 / 0 | |
| 1.94.57 | 0 / 0 | |
| 1.94.56 | 0 / 0 | |
| 1.94.55 | 0 / 0 | |
| 1.94.54 | 0 / 0 | |
| 1.94.53 | 0 / 0 | |
| 1.94.52 | 0 / 0 | |
| 1.94.51 | 0 / 0 | |
| 1.94.50 | 0 / 0 | |
| 1.94.49 | 0 / 0 | |
| 1.94.48 | 0 / 0 | |
| 1.94.47 | 0 / 0 | |
| 1.94.46 | 0 / 0 | |
| 1.94.45 | 0 / 0 | |
| 1.94.44 | 0 / 0 | |
| 1.94.43 | 0 / 0 | |
| 1.94.42 | 0 / 0 | |
| 1.94.41 | 0 / 0 | |
| 1.94.40 | 0 / 0 | |
| 1.94.39 | 0 / 0 | |
| 1.94.38 | 0 / 0 | |
| 1.94.37 | 0 / 0 | |
| 1.94.36 | 0 / 0 | |
| 1.94.35 | 0 / 0 | |
| 1.94.34 | 0 / 0 | |
| 1.94.33 | 0 / 0 | |
| 1.94.32 | 0 / 0 | |
| 1.94.31 | 0 / 0 |
v1.94.81
6 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.80
6 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.79
6 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.78
6 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.77
6 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.76
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.75
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.74
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.73
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.72
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.71
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.70
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.69
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.68
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.67
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.66
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.65
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.64
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.63
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.62
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.61
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.60
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.59
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.58
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.57
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.56
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.55
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.54
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.53
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.