@wix/auto_sdk_table-reservations_reservation-locations
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/table-reservations-v1-reservation-location-reservation-locations.universal-sNJBADjo.d.mts | AI (source-diff): Generated TypeScript declaration file; long lines are interface/type exports, not obfuscation. | ai | |
| source-diff | obfuscated-file:build/internal/cjs/table-reservations-v1-reservation-location-reservation-locations.universal-sNJBADjo.d.ts | AI (source-diff): Same — generated declaration file from Wix SDK build pipeline. | ai | |
| source-diff | obfuscated-file:build/cjs/table-reservations-v1-reservation-location-reservation-locations.universal-sNJBADjo.d.ts | AI (source-diff): Generated TypeScript declaration file; long lines are type exports, not obfuscation. | ai | |
| source-diff | obfuscated-file:build/internal/es/table-reservations-v1-reservation-location-reservation-locations.universal-sNJBADjo.d.mts | AI (source-diff): Same — generated declaration file from Wix SDK build pipeline. | ai | |
| source-diff | obfuscated-file:build/internal/es/table-reservations-v1-reservation-location-reservation-locations.universal-BsmyuKI4.d.mts | AI (source-diff): Generated TS declaration file; same pattern as other Wix SDK packages. | ai | |
| source-diff | obfuscated-file:build/internal/cjs/table-reservations-v1-reservation-location-reservation-locations.universal-BsmyuKI4.d.ts | AI (source-diff): Generated TS declaration file; same Wix SDK build pattern. | ai | |
| source-diff | obfuscated-file:build/cjs/table-reservations-v1-reservation-location-reservation-locations.universal-BsmyuKI4.d.ts | AI (source-diff): Generated TS declaration file; long lines are type exports, not obfuscation. | ai | |
| source-diff | obfuscated-file:build/es/table-reservations-v1-reservation-location-reservation-locations.universal-BsmyuKI4.d.mts | AI (source-diff): Generated TS declaration file; long lines are interface/type exports, not obfuscation. | ai | |
| source-diff | obfuscated-file:build/internal/table-reservations-v1-reservation-location-reservation-locations.universal-DAXnc7VN.d.ts | AI (source-diff): Bundled TypeScript declaration file; false positive. | ai | |
| source-diff | obfuscated-file:build/internal/table-reservations-v1-reservation-location-reservation-locations.universal-DAXnc7VN.d.mts | AI (source-diff): Bundled TypeScript declaration file; false positive. | ai | |
| source-diff | obfuscated-file:build/table-reservations-v1-reservation-location-reservation-locations.universal-DAXnc7VN.d.mts | AI (source-diff): Bundled TypeScript declaration file; false positive. | ai | |
| source-diff | obfuscated-file:build/table-reservations-v1-reservation-location-reservation-locations.universal-DAXnc7VN.d.ts | AI (source-diff): Bundled TypeScript declaration file; false positive. | ai | |
| source-diff | obfuscated-file:build/table-reservations-v1-reservation-location-reservation-locations.universal-DT_NcW8G.d.mts | AI (source-diff): Bundled TypeScript declaration file; long lines are re-exports, not obfuscation. | ai | |
| source-diff | obfuscated-file:build/internal/table-reservations-v1-reservation-location-reservation-locations.universal-DT_NcW8G.d.mts | AI (source-diff): Bundled TypeScript declaration file; long lines are re-exports, not obfuscation. | ai | |
| source-diff | obfuscated-file:build/internal/index.d.mts | AI (source-diff): Same bundled .d.mts pattern; stable false positive for this package family. | ai | |
| source-diff | obfuscated-file:build/index.d.mts | AI (source-diff): Long-line TypeScript declaration files are standard output of Wix SDK bundler (tsup); not obfuscation. | ai | |
| source-diff | obfuscated-file:build/table-reservations-v1-reservation-location-reservation-locations.universal-DT_NcW8G.d.ts | AI (source-diff): Bundled TypeScript declaration file; long lines are re-exports, not obfuscation. | ai | |
| source-diff | obfuscated-file:build/internal/table-reservations-v1-reservation-location-reservation-locations.universal-DT_NcW8G.d.ts | AI (source-diff): Bundled TypeScript declaration file; long lines are re-exports, not obfuscation. | ai | |
| source-diff | obfuscated-file:build/internal/index.d.ts | AI (source-diff): Bundled TypeScript declaration file; long lines are re-exports, not obfuscation. | ai | |
| source-diff | obfuscated-file:build/index.d.ts | AI (source-diff): Bundled TypeScript declaration file; long lines are re-exports, not obfuscation. | ai | |
| source-diff | obfuscated-file:build/es/table-reservations-v1-reservation-location-reservation-locations.universal-DAXnc7VN.d.mts | AI (source-diff): Readable TypeScript interface declarations; long lines from bundled type exports, not obfuscation. | ai | |
| source-diff | obfuscated-file:build/internal/es/table-reservations-v1-reservation-location-reservation-locations.universal-DAXnc7VN.d.mts | AI (source-diff): Same as above; standard tsup declaration output. | ai | |
| source-diff | obfuscated-file:build/cjs/table-reservations-v1-reservation-location-reservation-locations.universal-DAXnc7VN.d.ts | AI (source-diff): CJS variant of the same declaration file pattern; not obfuscated. | ai | |
| source-diff | obfuscated-file:build/internal/cjs/table-reservations-v1-reservation-location-reservation-locations.universal-DAXnc7VN.d.ts | AI (source-diff): Internal CJS declaration file; same tsup bundle pattern. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Consistent with Wix org-wide maintainer restructuring; wix-ci-publisher is a known trusted CI account. | ai | |
| source-diff | obfuscated-file:build/internal/es/meta.d.mts | AI (source-diff): TypeScript declaration file with long export lists; standard Wix SDK build output, not obfuscation. | ai | |
| source-diff | obfuscated-file:build/es/meta.d.mts | AI (source-diff): TypeScript declaration file with long export lists; standard Wix SDK build output, not obfuscation. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Maintainer removal consistent with Wix CI publisher consolidation. | ai | |
| source-diff | obfuscated-file:build/internal/es/index.d.mts | AI (source-diff): Same pattern — auto-generated .d.mts with long export lines; stable for this package. | ai | |
| source-diff | obfuscated-file:build/es/index.typings.d.mts | AI (source-diff): Generated typings file with long lines; not obfuscation. | ai | |
| source-diff | obfuscated-file:build/internal/es/index.typings.d.mts | AI (source-diff): Generated typings file with long lines; not obfuscation. | ai | |
| source-diff | obfuscated-file:build/es/index.d.mts | AI (source-diff): Long-line TypeScript declaration file generated by Wix SDK build pipeline; not obfuscation. | ai | |
| provenance | publisher-changed | AI (provenance): Transition to wix-ci-publisher is a known Wix org-wide CI migration pattern; stable for this package. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Wix auto-generated SDK; missing description is expected across all versions. | ai | |
| provenance | no-provenance | AI (provenance): Wix CI pipeline does not attach Sigstore provenance; consistent across all Wix auto SDK packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Wix auto-generated SDK packages intentionally lack descriptions, repos, and keywords; mass-production pattern is by design. | ai |
Versions (showing 51 of 78)
| Version | Deps | Published |
|---|---|---|
| 1.0.91 | 3 / 2 | |
| 1.0.90 | 3 / 2 | |
| 1.0.89 | 3 / 2 | |
| 1.0.88 | 3 / 2 | |
| 1.0.87 | 3 / 2 | |
| 1.0.86 | 3 / 2 | |
| 1.0.85 | 3 / 2 | |
| 1.0.84 | 3 / 2 | |
| 1.0.83 | 3 / 2 | |
| 1.0.82 | 3 / 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 |
v1.0.91
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.90
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.89
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.88
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.87
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.84
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.83
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.82
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.81
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.80
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.79
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.78
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.77
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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
8 findingsThis version was published by a different npm account than previous versions on 2025-10-23. This could indicate a legitimate maintainer transition or an account compromise.
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.52
8 findingsThis version was published by a different npm account than previous versions on 2025-10-15. This could indicate a legitimate maintainer transition or an account compromise.
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.51
8 findingsThis version was published by a different npm account than previous versions on 2025-10-15. This could indicate a legitimate maintainer transition or an account compromise.
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.50
6 findingsThis version was published by a different npm account than previous versions on 2025-08-28. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.49
6 findingsThis version was published by a different npm account than previous versions on 2025-08-28. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.48
6 findingsThis version was published by a different npm account than previous versions on 2025-08-14. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.47
6 findingsThis version was published by a different npm account than previous versions on 2025-07-25. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.46
6 findingsThis version was published by a different npm account than previous versions on 2025-07-23. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.45
6 findingsThis version was published by a different npm account than previous versions on 2025-07-21. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.44
6 findingsThis version was published by a different npm account than previous versions on 2025-07-21. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.43
6 findingsThis version was published by a different npm account than previous versions on 2025-07-16. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.42
6 findingsThis version was published by a different npm account than previous versions on 2025-07-03. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.41
6 findingsThis version was published by a different npm account than previous versions on 2025-07-03. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.