@wix/auto_sdk_stores_read-only-variants-v-3
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:build/es/stores-catalog-v3-read-only-variant-read-only-variants-v-3.universal-BLnK7bTl.d.mts | AI (source-diff): Large .d.mts TypeScript declaration file with long lines from generated type definitions; not executable obfuscated code. | ai | |
| source-diff | obfuscated-file:build/internal/cjs/stores-catalog-v3-read-only-variant-read-only-variants-v-3.universal-BVbbWcjf.d.ts | AI (source-diff): Large .d.ts TypeScript declaration file with long lines from generated type definitions; not executable obfuscated code. | ai | |
| source-diff | obfuscated-file:build/cjs/stores-catalog-v3-read-only-variant-read-only-variants-v-3.universal-BLnK7bTl.d.ts | AI (source-diff): Large .d.ts TypeScript declaration file with long lines from generated type definitions; not executable obfuscated code. | ai | |
| source-diff | obfuscated-file:build/internal/es/stores-catalog-v3-read-only-variant-read-only-variants-v-3.universal-BVbbWcjf.d.mts | AI (source-diff): Large .d.mts TypeScript declaration file with long lines from generated type definitions; not executable obfuscated code. | ai | |
| source-diff | obfuscated-file:build/es/stores-catalog-v3-read-only-variant-read-only-variants-v-3.universal-CgSVrIae.d.mts | AI (source-diff): TypeScript declaration file with long lines from complex type unions; readable JSDoc content, not obfuscation. | ai | |
| source-diff | obfuscated-file:build/cjs/stores-catalog-v3-read-only-variant-read-only-variants-v-3.universal-CgSVrIae.d.ts | AI (source-diff): TypeScript declaration file with long lines from complex type unions; readable JSDoc content, not obfuscation. | ai | |
| source-diff | obfuscated-file:build/internal/cjs/stores-catalog-v3-read-only-variant-read-only-variants-v-3.universal-BhYimHEe.d.ts | AI (source-diff): TypeScript declaration file with long lines from complex type unions; readable JSDoc content, not obfuscation. | ai | |
| source-diff | obfuscated-file:build/internal/es/stores-catalog-v3-read-only-variant-read-only-variants-v-3.universal-BhYimHEe.d.mts | AI (source-diff): TypeScript declaration file with long lines from complex type unions; readable JSDoc content, not obfuscation. | ai | |
| source-diff | obfuscated-file:build/es/stores-catalog-v3-read-only-variant-read-only-variants-v-3.universal-DhqxV43r.d.mts | AI (source-diff): Generated TypeScript declaration file with long lines from type unions; not obfuscated code. | ai | |
| source-diff | obfuscated-file:build/cjs/stores-catalog-v3-read-only-variant-read-only-variants-v-3.universal-DhqxV43r.d.ts | AI (source-diff): Generated TypeScript declaration file with long lines from type unions; not obfuscated code. | ai | |
| source-diff | obfuscated-file:build/internal/cjs/stores-catalog-v3-read-only-variant-read-only-variants-v-3.universal-BWl05dv4.d.ts | AI (source-diff): Generated TypeScript declaration file with long lines from type unions; not obfuscated code. | ai | |
| source-diff | obfuscated-file:build/internal/es/stores-catalog-v3-read-only-variant-read-only-variants-v-3.universal-BWl05dv4.d.mts | AI (source-diff): Generated TypeScript declaration file with long lines from type unions; not obfuscated code. | ai | |
| source-diff | obfuscated-file:build/es/stores-catalog-v3-read-only-variant-read-only-variants-v-3.universal-CEB6reGR.d.mts | AI (source-diff): Long-line TypeScript declaration files from Wix SDK codegen; not obfuscated code. | ai | |
| source-diff | obfuscated-file:build/internal/cjs/stores-catalog-v3-read-only-variant-read-only-variants-v-3.universal-o-qjRWP7.d.ts | AI (source-diff): Long-line TypeScript declaration files from Wix SDK codegen; not obfuscated code. | ai | |
| source-diff | obfuscated-file:build/cjs/stores-catalog-v3-read-only-variant-read-only-variants-v-3.universal-CEB6reGR.d.ts | AI (source-diff): Long-line TypeScript declaration files from Wix SDK codegen; not obfuscated code. | ai | |
| source-diff | obfuscated-file:build/internal/es/stores-catalog-v3-read-only-variant-read-only-variants-v-3.universal-o-qjRWP7.d.mts | AI (source-diff): Long-line TypeScript declaration files from Wix SDK codegen; not obfuscated code. | ai | |
| source-diff | obfuscated-file:build/es/stores-catalog-v3-read-only-variant-read-only-variants-v-3.universal-Bzr5oXEa.d.mts | AI (source-diff): TypeScript declaration file with long lines from dense JSDoc type definitions; not obfuscated code. | ai | |
| source-diff | obfuscated-file:build/cjs/stores-catalog-v3-read-only-variant-read-only-variants-v-3.universal-Bzr5oXEa.d.ts | AI (source-diff): TypeScript declaration file with long lines from dense JSDoc type definitions; not obfuscated code. | ai | |
| source-diff | obfuscated-file:build/internal/cjs/stores-catalog-v3-read-only-variant-read-only-variants-v-3.universal-B6vvkdMz.d.ts | AI (source-diff): TypeScript declaration file with long lines from dense JSDoc type definitions; not obfuscated code. | ai | |
| source-diff | obfuscated-file:build/internal/es/stores-catalog-v3-read-only-variant-read-only-variants-v-3.universal-B6vvkdMz.d.mts | AI (source-diff): TypeScript declaration file with long lines from dense JSDoc type definitions; not obfuscated code. | ai | |
| source-diff | obfuscated-file:build/es/stores-catalog-v3-read-only-variant-read-only-variants-v-3.universal-CmfOuHQ7.d.mts | AI (source-diff): TypeScript declaration file with long lines from dense JSDoc type definitions; not obfuscated code. | ai | |
| source-diff | obfuscated-file:build/cjs/stores-catalog-v3-read-only-variant-read-only-variants-v-3.universal-CmfOuHQ7.d.ts | AI (source-diff): TypeScript declaration file with long lines from dense JSDoc type definitions; not obfuscated code. | ai | |
| source-diff | obfuscated-file:build/internal/cjs/stores-catalog-v3-read-only-variant-read-only-variants-v-3.universal-B1rdilVM.d.ts | AI (source-diff): TypeScript declaration file with long lines from dense JSDoc type definitions; not obfuscated code. | ai | |
| source-diff | obfuscated-file:build/internal/es/stores-catalog-v3-read-only-variant-read-only-variants-v-3.universal-B1rdilVM.d.mts | AI (source-diff): TypeScript declaration file with long lines from dense JSDoc type definitions; not obfuscated code. | ai | |
| source-diff | obfuscated-file:build/internal/es/stores-catalog-v3-read-only-variant-read-only-variants-v-3.universal-DCMFkmPS.d.mts | AI (source-diff): Large .d.mts type declaration file with long lines from generated TypeScript types; not actual obfuscation. | ai | |
| source-diff | obfuscated-file:build/es/stores-catalog-v3-read-only-variant-read-only-variants-v-3.universal-C96yax26.d.mts | AI (source-diff): Large .d.mts type declaration file with long lines from generated TypeScript types; not actual obfuscation. | ai | |
| source-diff | obfuscated-file:build/cjs/stores-catalog-v3-read-only-variant-read-only-variants-v-3.universal-C96yax26.d.ts | AI (source-diff): Large .d.ts type declaration file with long lines from generated TypeScript types; not actual obfuscation. | ai | |
| source-diff | obfuscated-file:build/internal/cjs/stores-catalog-v3-read-only-variant-read-only-variants-v-3.universal-DCMFkmPS.d.ts | AI (source-diff): Large .d.ts type declaration file with long lines from generated TypeScript types; not actual obfuscation. | ai | |
| source-diff | obfuscated-file:build/es/stores-catalog-v3-read-only-variant-read-only-variants-v-3.universal-6yC0ejoi.d.mts | AI (source-diff): TypeScript declaration file with long lines from dense type definitions, not obfuscated code. Stable pattern for Wix SDK packages. | ai | |
| source-diff | obfuscated-file:build/internal/cjs/stores-catalog-v3-read-only-variant-read-only-variants-v-3.universal-cOyVMu7V.d.ts | AI (source-diff): TypeScript declaration file with long lines from dense type definitions, not obfuscated code. Stable pattern for Wix SDK packages. | ai | |
| source-diff | obfuscated-file:build/cjs/stores-catalog-v3-read-only-variant-read-only-variants-v-3.universal-6yC0ejoi.d.ts | AI (source-diff): TypeScript declaration file with long lines from dense type definitions, not obfuscated code. Stable pattern for Wix SDK packages. | ai | |
| source-diff | obfuscated-file:build/internal/es/stores-catalog-v3-read-only-variant-read-only-variants-v-3.universal-cOyVMu7V.d.mts | AI (source-diff): TypeScript declaration file with long lines from dense type definitions, not obfuscated code. Stable pattern for Wix SDK packages. | ai | |
| source-diff | obfuscated-file:build/internal/es/stores-catalog-v3-read-only-variant-read-only-variants-v-3.universal-CoUSBFoZ.d.mts | AI (source-diff): Long-line TypeScript declaration files from Wix SDK build pipeline; not obfuscated code. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Wix internal team rotation via known CI publisher; stable pattern across Wix SDK packages. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Wix internal team rotation via known CI publisher; stable pattern across Wix SDK packages. | ai | |
| source-diff | obfuscated-file:build/internal/cjs/stores-catalog-v3-read-only-variant-read-only-variants-v-3.universal-CoUSBFoZ.d.ts | AI (source-diff): Long-line TypeScript declaration files from Wix SDK build pipeline; not obfuscated code. | ai | |
| source-diff | obfuscated-file:build/internal/es/stores-catalog-v3-read-only-variant-read-only-variants-v-3.universal-DHHbzvlL.d.mts | AI (source-diff): Same pattern: generated .d.mts with long lines; readable JSDoc content, not obfuscation. | ai | |
| source-diff | obfuscated-file:build/internal/cjs/stores-catalog-v3-read-only-variant-read-only-variants-v-3.universal-DHHbzvlL.d.ts | AI (source-diff): Generated TypeScript declaration file; long lines from type unions, not obfuscation. | ai | |
| source-diff | obfuscated-file:build/es/stores-catalog-v3-read-only-variant-read-only-variants-v-3.universal-B4G2snUA.d.mts | AI (source-diff): Long-line TypeScript declaration file with readable JSDoc comments; not obfuscated code. | ai | |
| source-diff | obfuscated-file:build/cjs/stores-catalog-v3-read-only-variant-read-only-variants-v-3.universal-B4G2snUA.d.ts | AI (source-diff): Long-line TypeScript declaration file with readable JSDoc comments; not obfuscated code. | ai | |
| source-diff | obfuscated-file:build/internal/es/stores-catalog-v3-read-only-variant-read-only-variants-v-3.universal-CLm4D_cs.d.mts | AI (source-diff): Long-line TypeScript declaration file with readable JSDoc comments; not obfuscated code. | ai | |
| source-diff | obfuscated-file:build/internal/cjs/stores-catalog-v3-read-only-variant-read-only-variants-v-3.universal-CLm4D_cs.d.ts | AI (source-diff): Long-line TypeScript declaration file with readable JSDoc comments; not obfuscated code. | ai | |
| source-diff | obfuscated-file:build/internal/es/stores-catalog-v3-read-only-variant-read-only-variants-v-3.universal-CpQG0qBc.d.mts | AI (source-diff): TypeScript declaration file with long lines from dense JSDoc type definitions; not obfuscated code. | ai | |
| source-diff | obfuscated-file:build/internal/cjs/stores-catalog-v3-read-only-variant-read-only-variants-v-3.universal-CpQG0qBc.d.ts | AI (source-diff): TypeScript declaration file with long lines from dense JSDoc type definitions; not obfuscated code. | ai | |
| source-diff | obfuscated-file:build/cjs/stores-catalog-v3-read-only-variant-read-only-variants-v-3.universal-CS_KYDkd.d.ts | AI (source-diff): TypeScript declaration file with long lines from dense JSDoc type definitions; not obfuscated code. | ai | |
| source-diff | obfuscated-file:build/es/stores-catalog-v3-read-only-variant-read-only-variants-v-3.universal-CS_KYDkd.d.mts | AI (source-diff): TypeScript declaration file with long lines from dense JSDoc type definitions; not obfuscated code. | ai | |
| source-diff | obfuscated-file:build/es/stores-catalog-v3-read-only-variant-read-only-variants-v-3.universal-CVSqB21b.d.mts | AI (source-diff): TypeScript declaration file with long lines from auto-generated type definitions; not executable obfuscated code. | ai | |
| source-diff | obfuscated-file:build/cjs/stores-catalog-v3-read-only-variant-read-only-variants-v-3.universal-CVSqB21b.d.ts | AI (source-diff): TypeScript declaration file with long lines from auto-generated type definitions; not executable obfuscated code. | ai | |
| source-diff | obfuscated-file:build/internal/cjs/stores-catalog-v3-read-only-variant-read-only-variants-v-3.universal-CjZpSmUu.d.ts | AI (source-diff): TypeScript declaration file with long lines from auto-generated type definitions; not executable obfuscated code. | ai | |
| source-diff | obfuscated-file:build/internal/es/stores-catalog-v3-read-only-variant-read-only-variants-v-3.universal-CjZpSmUu.d.mts | AI (source-diff): TypeScript declaration file with long lines from auto-generated type definitions; not executable obfuscated code. | ai | |
| provenance | no-provenance | AI (provenance): Wix CI publisher does not attach Sigstore provenance; consistent across all approved versions. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Wix auto-generated SDK package; templated name, no description/repo are expected for this publisher's pattern. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Wix auto-generated SDK packages consistently lack descriptions; stable false positive for this publisher. | ai |
Versions (showing 100 of 108)
| Version | Deps | Published |
|---|---|---|
| 1.0.125 | 3 / 2 | |
| 1.0.124 | 3 / 2 | |
| 1.0.123 | 3 / 2 | |
| 1.0.122 | 3 / 2 | |
| 1.0.121 | 3 / 2 | |
| 1.0.120 | 3 / 2 | |
| 1.0.119 | 3 / 2 | |
| 1.0.118 | 3 / 2 | |
| 1.0.117 | 3 / 2 | |
| 1.0.116 | 3 / 2 | |
| 1.0.115 | 3 / 2 | |
| 1.0.114 | 3 / 2 | |
| 1.0.113 | 3 / 2 | |
| 1.0.112 | 3 / 2 | |
| 1.0.111 | 3 / 2 | |
| 1.0.110 | 3 / 2 | |
| 1.0.109 | 3 / 2 | |
| 1.0.90 | 2 / 2 | |
| 1.0.89 | 2 / 2 | |
| 1.0.88 | 2 / 2 | |
| 1.0.87 | 2 / 2 | |
| 1.0.86 | 2 / 2 | |
| 1.0.85 | 2 / 2 | |
| 1.0.84 | 2 / 2 | |
| 1.0.83 | 2 / 2 | |
| 1.0.82 | 2 / 2 | |
| 1.0.81 | 2 / 2 | |
| 1.0.80 | 2 / 2 | |
| 1.0.79 | 2 / 2 | |
| 1.0.78 | 2 / 2 | |
| 1.0.77 | 2 / 2 | |
| 1.0.76 | 2 / 2 | |
| 1.0.75 | 2 / 2 | |
| 1.0.74 | 2 / 2 | |
| 1.0.73 | 2 / 2 | |
| 1.0.72 | 2 / 2 | |
| 1.0.71 | 2 / 2 | |
| 1.0.70 | 2 / 2 | |
| 1.0.69 | 2 / 2 | |
| 1.0.68 | 2 / 2 | |
| 1.0.67 | 2 / 2 | |
| 1.0.66 | 2 / 2 | |
| 1.0.65 | 2 / 2 | |
| 1.0.64 | 2 / 2 | |
| 1.0.63 | 2 / 2 | |
| 1.0.62 | 2 / 2 | |
| 1.0.61 | 2 / 2 | |
| 1.0.60 | 2 / 2 | |
| 1.0.59 | 2 / 2 | |
| 1.0.58 | 2 / 2 | |
| 1.0.57 | 2 / 2 | |
| 1.0.56 | 2 / 2 | |
| 1.0.55 | 2 / 2 | |
| 1.0.54 | 2 / 2 | |
| 1.0.53 | 2 / 2 | |
| 1.0.52 | 2 / 2 | |
| 1.0.51 | 2 / 2 | |
| 1.0.50 | 2 / 2 | |
| 1.0.49 | 2 / 2 | |
| 1.0.48 | 2 / 2 | |
| 1.0.47 | 2 / 2 | |
| 1.0.46 | 2 / 2 | |
| 1.0.45 | 2 / 2 | |
| 1.0.44 | 2 / 2 | |
| 1.0.43 | 2 / 2 | |
| 1.0.42 | 2 / 2 | |
| 1.0.41 | 2 / 2 | |
| 1.0.40 | 2 / 2 | |
| 1.0.39 | 2 / 2 | |
| 1.0.38 | 2 / 2 | |
| 1.0.37 | 2 / 2 | |
| 1.0.36 | 2 / 2 | |
| 1.0.35 | 2 / 2 | |
| 1.0.34 | 2 / 2 | |
| 1.0.33 | 2 / 2 | |
| 1.0.32 | 2 / 2 | |
| 1.0.31 | 2 / 2 | |
| 1.0.30 | 2 / 2 | |
| 1.0.29 | 2 / 2 | |
| 1.0.28 | 2 / 2 | |
| 1.0.27 | 2 / 2 | |
| 1.0.26 | 2 / 2 | |
| 1.0.25 | 2 / 2 | |
| 1.0.24 | 2 / 2 | |
| 1.0.23 | 2 / 2 | |
| 1.0.22 | 2 / 2 | |
| 1.0.21 | 2 / 2 | |
| 1.0.20 | 2 / 2 | |
| 1.0.19 | 2 / 2 | |
| 1.0.18 | 2 / 2 | |
| 1.0.17 | 2 / 2 | |
| 1.0.16 | 2 / 2 | |
| 1.0.15 | 2 / 2 | |
| 1.0.14 | 2 / 2 | |
| 1.0.13 | 2 / 2 | |
| 1.0.12 | 2 / 2 | |
| 1.0.11 | 2 / 2 | |
| 1.0.10 | 2 / 1 | |
| 1.0.9 | 2 / 1 | |
| 1.0.8 | 2 / 1 |
v1.0.125
5 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.124
5 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.123
5 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.122
5 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.121
5 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.120
5 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.119
5 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.118
5 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.117
5 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.116
5 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.115
5 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.114
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.113
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.111
5 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.110
5 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.109
5 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.90
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.89
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.88
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.87
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.86
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.85
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.84
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.83
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.82
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.81
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.80
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.79
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.78
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.77
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.76
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.75
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.74
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.73
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.72
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.71
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.70
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.69
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.68
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.67
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.66
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.65
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.64
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.63
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.62
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.61
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.60
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.59
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.58
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.57
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.34
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.33
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.32
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.31
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.30
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.29
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.28
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.27
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.26
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.25
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.24
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.23
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.22
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.21
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.20
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.19
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.18
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.17
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.16
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.15
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.14
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.13
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.12
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.11
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.10
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.9
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.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.