@wix/auto_sdk_get-paid_payment-link-payments
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/meta.d.mts | AI (source-diff): TypeScript declaration file with long re-export lines; standard Wix SDK build artifact. | ai | |
| source-diff | obfuscated-file:build/es/meta.d.mts | AI (source-diff): TypeScript declaration file with long re-export lines; standard Wix SDK build artifact. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Wix internal team rotation via trusted wix-ci-publisher account. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Wix internal team rotation via trusted wix-ci-publisher account. | ai | |
| source-diff | obfuscated-file:build/internal/cjs/paymentlinks-payments-v1-payment-link-payment-payment-link-payments.universal-Db8Aqqv0.d.ts | AI (source-diff): TypeScript declaration file with long lines from generated complex generics; not obfuscated code. | ai | |
| source-diff | obfuscated-file:build/cjs/paymentlinks-payments-v1-payment-link-payment-payment-link-payments.universal-Db8Aqqv0.d.ts | AI (source-diff): TypeScript declaration file with long lines from generated complex generics; not obfuscated code. | ai | |
| source-diff | obfuscated-file:build/internal/es/paymentlinks-payments-v1-payment-link-payment-payment-link-payments.universal-Db8Aqqv0.d.mts | AI (source-diff): TypeScript declaration file with long lines from generated complex generics; not obfuscated code. | ai | |
| source-diff | obfuscated-file:build/es/paymentlinks-payments-v1-payment-link-payment-payment-link-payments.universal-Db8Aqqv0.d.mts | AI (source-diff): TypeScript declaration file with long lines from generated complex generics; not obfuscated code. | ai | |
| source-diff | obfuscated-file:build/internal/cjs/paymentlinks-payments-v1-payment-link-payment-payment-link-payments.universal-Cpm6Yldo.d.ts | AI (source-diff): TypeScript declaration file with long lines from dense type definitions; not obfuscated code. | ai | |
| source-diff | obfuscated-file:build/cjs/paymentlinks-payments-v1-payment-link-payment-payment-link-payments.universal-Cpm6Yldo.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/es/paymentlinks-payments-v1-payment-link-payment-payment-link-payments.universal-Cpm6Yldo.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/paymentlinks-payments-v1-payment-link-payment-payment-link-payments.universal-Cpm6Yldo.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/paymentlinks-payments-v1-payment-link-payment-payment-link-payments.universal-rYai57-5.d.mts | AI (source-diff): Auto-generated TS declaration file; long lines are type definitions, not obfuscation. | ai | |
| source-diff | obfuscated-file:build/es/paymentlinks-payments-v1-payment-link-payment-payment-link-payments.universal-rYai57-5.d.mts | AI (source-diff): Auto-generated TS declaration file; long lines are type definitions, not obfuscation. | ai | |
| source-diff | obfuscated-file:build/internal/cjs/paymentlinks-payments-v1-payment-link-payment-payment-link-payments.universal-rYai57-5.d.ts | AI (source-diff): Auto-generated TS declaration file; long lines are type definitions, not obfuscation. | ai | |
| source-diff | obfuscated-file:build/cjs/paymentlinks-payments-v1-payment-link-payment-payment-link-payments.universal-rYai57-5.d.ts | AI (source-diff): Auto-generated TS declaration file; long lines are type definitions, not obfuscation. | ai | |
| source-diff | obfuscated-file:build/internal/paymentlinks-payments-v1-payment-link-payment-payment-link-payments.universal-DGlKjrJy.d.mts | AI (source-diff): TypeScript declaration file with long lines from bundled types; not obfuscated code. | ai | |
| source-diff | obfuscated-file:build/paymentlinks-payments-v1-payment-link-payment-payment-link-payments.universal-DGlKjrJy.d.mts | AI (source-diff): TypeScript declaration file with long lines from bundled types; not obfuscated code. | ai | |
| source-diff | obfuscated-file:build/paymentlinks-payments-v1-payment-link-payment-payment-link-payments.universal-DGlKjrJy.d.ts | AI (source-diff): TypeScript declaration file with long lines from bundled types; not obfuscated code. | ai | |
| source-diff | obfuscated-file:build/internal/paymentlinks-payments-v1-payment-link-payment-payment-link-payments.universal-DGlKjrJy.d.ts | AI (source-diff): TypeScript declaration file with long lines from bundled types; not obfuscated code. | ai | |
| source-diff | obfuscated-file:build/internal/cjs/paymentlinks-payments-v1-payment-link-payment-payment-link-payments.universal-DGlKjrJy.d.ts | AI (source-diff): TypeScript declaration file with long lines from verbose JSDoc; not obfuscated code. | ai | |
| source-diff | obfuscated-file:build/es/paymentlinks-payments-v1-payment-link-payment-payment-link-payments.universal-DGlKjrJy.d.mts | AI (source-diff): TypeScript declaration file with long lines from verbose JSDoc; not obfuscated code. | ai | |
| source-diff | obfuscated-file:build/internal/es/paymentlinks-payments-v1-payment-link-payment-payment-link-payments.universal-DGlKjrJy.d.mts | AI (source-diff): TypeScript declaration file with long lines from verbose JSDoc; not obfuscated code. | ai | |
| source-diff | obfuscated-file:build/cjs/paymentlinks-payments-v1-payment-link-payment-payment-link-payments.universal-DGlKjrJy.d.ts | AI (source-diff): TypeScript declaration file with long lines from verbose JSDoc; not obfuscated code. | ai | |
| source-diff | obfuscated-file:build/internal/cjs/paymentlinks-payments-v1-payment-link-payment-payment-link-payments.universal-CyG_m71o.d.ts | AI (source-diff): TypeScript declaration file with long interface/type definitions; standard SDK build output. | ai | |
| source-diff | obfuscated-file:build/es/paymentlinks-payments-v1-payment-link-payment-payment-link-payments.universal-CyG_m71o.d.mts | AI (source-diff): TypeScript declaration file with long interface/type definitions; standard SDK build output. | ai | |
| source-diff | obfuscated-file:build/internal/es/paymentlinks-payments-v1-payment-link-payment-payment-link-payments.universal-CyG_m71o.d.mts | AI (source-diff): TypeScript declaration file with long interface/type definitions; standard SDK build output. | ai | |
| source-diff | obfuscated-file:build/cjs/paymentlinks-payments-v1-payment-link-payment-payment-link-payments.universal-CyG_m71o.d.ts | AI (source-diff): TypeScript declaration file with long interface/type definitions; standard SDK build output. | ai | |
| source-diff | obfuscated-file:build/internal/es/index.d.mts | AI (source-diff): Same pattern — bundled .d.mts type declaration, not obfuscated code. | ai | |
| source-diff | obfuscated-file:build/es/paymentlinks-payments-v1-payment-link-payment-payment-link-payments.universal-DP13Cdha.d.mts | AI (source-diff): Long-line type declaration file; standard Wix SDK build output. | ai | |
| source-diff | obfuscated-file:build/internal/es/index.typings.d.mts | AI (source-diff): Bundled TypeScript typings rollup; stable false positive for this package. | ai | |
| source-diff | obfuscated-file:build/es/index.typings.d.mts | AI (source-diff): Bundled TypeScript typings rollup; stable false positive for this package. | ai | |
| source-diff | obfuscated-file:build/es/index.d.mts | AI (source-diff): Long-line TypeScript declaration rollup; standard Wix SDK build artifact, not obfuscation. | ai | |
| source-diff | obfuscated-file:build/internal/cjs/paymentlinks-payments-v1-payment-link-payment-payment-link-payments.universal-DP13Cdha.d.ts | AI (source-diff): Long-line type declaration file; standard Wix SDK build output. | ai | |
| source-diff | obfuscated-file:build/cjs/paymentlinks-payments-v1-payment-link-payment-payment-link-payments.universal-DP13Cdha.d.ts | AI (source-diff): Long-line type declaration file; standard Wix SDK build output. | ai | |
| source-diff | obfuscated-file:build/internal/es/paymentlinks-payments-v1-payment-link-payment-payment-link-payments.universal-DP13Cdha.d.mts | AI (source-diff): Long-line type declaration file; standard Wix SDK build output. | ai | |
| source-diff | obfuscated-file:build/es/paymentlinks-payments-v1-payment-link-payment-payment-link-payments.universal-ByRcRZtK.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/cjs/paymentlinks-payments-v1-payment-link-payment-payment-link-payments.universal-ByRcRZtK.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/cjs/paymentlinks-payments-v1-payment-link-payment-payment-link-payments.universal-ByRcRZtK.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/paymentlinks-payments-v1-payment-link-payment-payment-link-payments.universal-ByRcRZtK.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 | |
| npm-metadata | no-description | AI (npm-metadata): Wix SDK auto-gen pipeline does not populate descriptions; stable false positive for this package family. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Wix auto-generated SDK packages intentionally lack descriptions, repos, and keywords; mass-production is by design. | ai |
Versions (showing 44 of 44)
| Version | Deps | Published |
|---|---|---|
| 1.0.54 | 3 / 2 | |
| 1.0.53 | 3 / 2 | |
| 1.0.52 | 3 / 2 | |
| 1.0.51 | 3 / 2 | |
| 1.0.50 | 3 / 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.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 / 1 | |
| 1.0.15 | 2 / 1 | |
| 1.0.14 | 2 / 1 | |
| 1.0.13 | 2 / 1 | |
| 1.0.12 | 2 / 1 | |
| 1.0.11 | 2 / 1 | |
| 1.0.10 | 2 / 1 |
v1.0.54
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.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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
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.48
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.47
1 findingPackage 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.45
1 findingPackage 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.29
11 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.
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.
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.28
9 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.
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.27
9 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.
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.26
9 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.
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.25
9 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.
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.24
9 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.
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.22
7 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.
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.21
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.20
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.19
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.18
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.17
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.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.