@wix/auto_sdk_ecom_abandoned-checkouts
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/internal/es/ecom-v1-abandoned-checkout-abandoned-checkouts.universal-CArYHAHL.d.mts | AI (source-diff): TypeScript declaration file with long lines from complex type unions; not obfuscated code. Stable pattern for Wix SDK packages. | ai | |
| source-diff | obfuscated-file:build/internal/cjs/ecom-v1-abandoned-checkout-abandoned-checkouts.universal-CArYHAHL.d.ts | AI (source-diff): TypeScript declaration file with long lines from complex type unions; not obfuscated code. Stable pattern for Wix SDK packages. | ai | |
| source-diff | obfuscated-file:build/internal/es/ecom-v1-abandoned-checkout-abandoned-checkouts.universal-DTc3f1_H.d.mts | AI (source-diff): TypeScript declaration file with long lines from JSDoc comments; not obfuscated code. Stable pattern for this Wix auto-SDK package. | ai | |
| source-diff | obfuscated-file:build/internal/cjs/ecom-v1-abandoned-checkout-abandoned-checkouts.universal-DTc3f1_H.d.ts | AI (source-diff): TypeScript declaration file with long lines from JSDoc comments; not obfuscated code. Stable pattern for this Wix auto-SDK package. | ai | |
| source-diff | obfuscated-file:build/cjs/ecom-v1-abandoned-checkout-abandoned-checkouts.universal-CCZj0Gfc.d.ts | AI (source-diff): TypeScript declaration file with long lines from JSDoc comments; not obfuscated code. Stable pattern for this Wix auto-SDK package. | ai | |
| source-diff | obfuscated-file:build/es/ecom-v1-abandoned-checkout-abandoned-checkouts.universal-CCZj0Gfc.d.mts | AI (source-diff): TypeScript declaration file with long lines from JSDoc comments; not obfuscated code. Stable pattern for this Wix auto-SDK package. | ai | |
| source-diff | obfuscated-file:build/internal/cjs/ecom-v1-abandoned-checkout-abandoned-checkouts.universal-Cc3dfanX.d.ts | AI (source-diff): TypeScript declaration file with JSDoc; long lines from bundled types, not obfuscation. Stable pattern for Wix auto-SDK packages. | ai | |
| source-diff | obfuscated-file:build/internal/es/ecom-v1-abandoned-checkout-abandoned-checkouts.universal-Cc3dfanX.d.mts | AI (source-diff): TypeScript declaration file with JSDoc; long lines from bundled types, not obfuscation. Stable pattern for Wix auto-SDK packages. | ai | |
| source-diff | obfuscated-file:build/internal/es/ecom-v1-abandoned-checkout-abandoned-checkouts.universal-BzhyfUMH.d.mts | AI (source-diff): TypeScript declaration file with long union type lines; not obfuscated code. Pattern is stable for Wix auto-SDK packages. | ai | |
| source-diff | obfuscated-file:build/es/ecom-v1-abandoned-checkout-abandoned-checkouts.universal-BvGmL8qg.d.mts | AI (source-diff): TypeScript declaration file with long union type lines; not obfuscated code. Pattern is stable for Wix auto-SDK packages. | ai | |
| source-diff | obfuscated-file:build/internal/cjs/ecom-v1-abandoned-checkout-abandoned-checkouts.universal-BzhyfUMH.d.ts | AI (source-diff): TypeScript declaration file with long union type lines; not obfuscated code. Pattern is stable for Wix auto-SDK packages. | ai | |
| source-diff | obfuscated-file:build/cjs/ecom-v1-abandoned-checkout-abandoned-checkouts.universal-BvGmL8qg.d.ts | AI (source-diff): TypeScript declaration file with long union type lines; not obfuscated code. Pattern is stable for Wix auto-SDK packages. | ai | |
| source-diff | obfuscated-file:build/es/ecom-v1-abandoned-checkout-abandoned-checkouts.universal-iC02NQVc.d.mts | AI (source-diff): TypeScript declaration file with JSDoc; long lines are generated type unions, not obfuscation. | ai | |
| source-diff | obfuscated-file:build/internal/es/ecom-v1-abandoned-checkout-abandoned-checkouts.universal-DuhDBWtW.d.mts | AI (source-diff): TypeScript declaration file with JSDoc; long lines are generated type unions, not obfuscation. | ai | |
| source-diff | obfuscated-file:build/internal/cjs/ecom-v1-abandoned-checkout-abandoned-checkouts.universal-DuhDBWtW.d.ts | AI (source-diff): TypeScript declaration file with JSDoc; long lines are generated type unions, not obfuscation. | ai | |
| source-diff | obfuscated-file:build/cjs/ecom-v1-abandoned-checkout-abandoned-checkouts.universal-iC02NQVc.d.ts | AI (source-diff): TypeScript declaration file with JSDoc; long lines are generated type unions, not obfuscation. | ai | |
| source-diff | obfuscated-file:build/es/ecom-v1-abandoned-checkout-abandoned-checkouts.universal-D7Tj5DAM.d.mts | AI (source-diff): TypeScript declaration file with long lines from dense type definitions; not executable obfuscated code. | ai | |
| source-diff | obfuscated-file:build/internal/cjs/ecom-v1-abandoned-checkout-abandoned-checkouts.universal-Be00Fxej.d.ts | AI (source-diff): TypeScript declaration file with long lines from dense type definitions; not executable obfuscated code. | ai | |
| source-diff | obfuscated-file:build/cjs/ecom-v1-abandoned-checkout-abandoned-checkouts.universal-D7Tj5DAM.d.ts | AI (source-diff): TypeScript declaration file with long lines from dense type definitions; not executable obfuscated code. | ai | |
| source-diff | obfuscated-file:build/internal/es/ecom-v1-abandoned-checkout-abandoned-checkouts.universal-Be00Fxej.d.mts | AI (source-diff): TypeScript declaration file with long lines from dense type definitions; not executable obfuscated code. | ai | |
| source-diff | obfuscated-file:build/cjs/ecom-v1-abandoned-checkout-abandoned-checkouts.universal-C8oWIE96.d.ts | AI (source-diff): TypeScript declaration file with long lines from dense type definitions; not obfuscated code. | ai | |
| source-diff | obfuscated-file:build/internal/cjs/ecom-v1-abandoned-checkout-abandoned-checkouts.universal-BpGTpVP7.d.ts | AI (source-diff): TypeScript declaration file with long lines from dense type definitions; not obfuscated code. | ai | |
| source-diff | obfuscated-file:build/es/ecom-v1-abandoned-checkout-abandoned-checkouts.universal-C8oWIE96.d.mts | AI (source-diff): TypeScript declaration file with long lines from dense type definitions; not obfuscated code. | ai | |
| source-diff | obfuscated-file:build/internal/es/ecom-v1-abandoned-checkout-abandoned-checkouts.universal-BpGTpVP7.d.mts | AI (source-diff): TypeScript declaration file with long lines from dense type definitions; not obfuscated code. | ai | |
| source-diff | obfuscated-file:build/es/ecom-v1-abandoned-checkout-abandoned-checkouts.universal-Clay04rF.d.mts | AI (source-diff): TypeScript declaration file with long generated type union lines; not executable obfuscated code. | ai | |
| source-diff | obfuscated-file:build/cjs/ecom-v1-abandoned-checkout-abandoned-checkouts.universal-Clay04rF.d.ts | AI (source-diff): TypeScript declaration file with long generated type union lines; not executable obfuscated code. | ai | |
| source-diff | obfuscated-file:build/internal/es/ecom-v1-abandoned-checkout-abandoned-checkouts.universal-50WaFSYL.d.mts | AI (source-diff): TypeScript declaration file with long generated type union lines; not executable obfuscated code. | ai | |
| source-diff | obfuscated-file:build/internal/cjs/ecom-v1-abandoned-checkout-abandoned-checkouts.universal-50WaFSYL.d.ts | AI (source-diff): TypeScript declaration file with long generated type union lines; not executable obfuscated code. | ai | |
| source-diff | obfuscated-file:build/es/ecom-v1-abandoned-checkout-abandoned-checkouts.universal-xMrPObPW.d.mts | AI (source-diff): TypeScript declaration file with long lines from generated type definitions; not obfuscated code. | ai | |
| source-diff | obfuscated-file:build/internal/es/ecom-v1-abandoned-checkout-abandoned-checkouts.universal-kgaKuR8n.d.mts | AI (source-diff): TypeScript declaration file with long lines from generated type definitions; not obfuscated code. | ai | |
| source-diff | obfuscated-file:build/cjs/ecom-v1-abandoned-checkout-abandoned-checkouts.universal-xMrPObPW.d.ts | AI (source-diff): TypeScript declaration file with long lines from generated type definitions; not obfuscated code. | ai | |
| source-diff | obfuscated-file:build/internal/cjs/ecom-v1-abandoned-checkout-abandoned-checkouts.universal-kgaKuR8n.d.ts | AI (source-diff): TypeScript declaration file with long lines from generated type definitions; not obfuscated code. | ai | |
| source-diff | obfuscated-file:build/internal/es/ecom-v1-abandoned-checkout-abandoned-checkouts.universal-Dr5KX94K.d.mts | AI (source-diff): TypeScript declaration file with long lines from dense type unions; not obfuscated code. Stable pattern for Wix auto-SDK packages. | ai | |
| source-diff | obfuscated-file:build/internal/cjs/ecom-v1-abandoned-checkout-abandoned-checkouts.universal-Dr5KX94K.d.ts | AI (source-diff): TypeScript declaration file with long lines from dense type unions; not obfuscated code. Stable pattern for Wix auto-SDK packages. | ai | |
| source-diff | obfuscated-file:build/cjs/ecom-v1-abandoned-checkout-abandoned-checkouts.universal-CTYB2h9T.d.ts | AI (source-diff): TypeScript declaration file with long lines from dense type unions; not obfuscated code. Stable pattern for Wix auto-SDK packages. | ai | |
| source-diff | obfuscated-file:build/es/ecom-v1-abandoned-checkout-abandoned-checkouts.universal-CTYB2h9T.d.mts | AI (source-diff): TypeScript declaration file with long lines from dense type unions; not obfuscated code. Stable pattern for Wix auto-SDK packages. | ai | |
| provenance | no-provenance | AI (provenance): Wix CI pipeline does not use Sigstore provenance; consistent across all approved versions. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Wix CI-generated SDK packages consistently omit descriptions; stable false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Wix auto-generated SDK stub; templated name, no description/repo are expected for this package family. | ai |
Versions (showing 51 of 70)
| Version | Deps | Published |
|---|---|---|
| 1.0.75 | 3 / 2 | |
| 1.0.74 | 3 / 2 | |
| 1.0.73 | 3 / 2 | |
| 1.0.72 | 3 / 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 |
v1.0.75
3 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.70
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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
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.46
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.45
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.44
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.43
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.42
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.41
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.40
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.39
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.38
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.37
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.36
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.35
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.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.