@wix/auto_sdk_restaurants_catalogs
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:build/internal/es/meta.d.mts | AI (source-diff): Long-line TypeScript declaration file with re-exported type aliases; standard Wix SDK build artifact. | ai | |
| source-diff | obfuscated-file:build/es/meta.d.mts | AI (source-diff): Long-line TypeScript declaration file with re-exported type aliases; standard Wix SDK build artifact. | ai | |
| source-diff | obfuscated-file:build/es/restaurants-catalogs-v3-catalog-catalogs.universal-DTKMFsV8.d.mts | AI (source-diff): TypeScript declaration file with long lines from concatenated API type definitions; not obfuscated code. | ai | |
| source-diff | obfuscated-file:build/internal/cjs/restaurants-catalogs-v3-catalog-catalogs.universal-DTKMFsV8.d.ts | AI (source-diff): TypeScript declaration file with long lines from concatenated API type definitions; not obfuscated code. | ai | |
| source-diff | obfuscated-file:build/cjs/restaurants-catalogs-v3-catalog-catalogs.universal-DTKMFsV8.d.ts | AI (source-diff): TypeScript declaration file with long lines from concatenated API type definitions; not obfuscated code. | ai | |
| source-diff | obfuscated-file:build/internal/es/restaurants-catalogs-v3-catalog-catalogs.universal-DTKMFsV8.d.mts | AI (source-diff): TypeScript declaration file with long lines from concatenated API type definitions; not obfuscated code. | ai | |
| source-diff | obfuscated-file:build/es/index.typings.d.mts | AI (source-diff): Generated TypeScript declaration file with long lines from bundled types; not obfuscated code. | ai | |
| source-diff | obfuscated-file:build/internal/es/index.typings.d.mts | AI (source-diff): Generated TypeScript declaration file with long lines from bundled types; not obfuscated code. | ai | |
| source-diff | obfuscated-file:build/restaurants-catalogs-v3-catalog-catalogs.universal-DTKMFsV8.d.mts | AI (source-diff): TypeScript declaration file with long JSDoc lines; not obfuscated code. Stable pattern for Wix auto-SDK packages. | ai | |
| source-diff | obfuscated-file:build/restaurants-catalogs-v3-catalog-catalogs.universal-DTKMFsV8.d.ts | AI (source-diff): TypeScript declaration file with long JSDoc lines; not obfuscated code. Stable pattern for Wix auto-SDK packages. | ai | |
| source-diff | obfuscated-file:build/internal/restaurants-catalogs-v3-catalog-catalogs.universal-DTKMFsV8.d.ts | AI (source-diff): TypeScript declaration file with long JSDoc lines; not obfuscated code. Stable pattern for Wix auto-SDK packages. | ai | |
| source-diff | obfuscated-file:build/internal/restaurants-catalogs-v3-catalog-catalogs.universal-DTKMFsV8.d.mts | AI (source-diff): TypeScript declaration file with long JSDoc lines; not obfuscated code. Stable pattern for Wix auto-SDK packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Auto-generated Wix SDK package; templated name/no-description pattern is stable across the entire @wix/auto_sdk_* family. | ai | |
| provenance | no-provenance | AI (provenance): Wix CI pipeline does not attach Sigstore provenance; consistent across all approved versions. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Intentionally empty description in auto-generated Wix SDK packages; stable pattern. | ai |
Versions (showing 72 of 72)
| Version | Deps | Published |
|---|---|---|
| 1.0.71 | 3 / 2 | |
| 1.0.70 | 3 / 2 | |
| 1.0.69 | 3 / 2 | |
| 1.0.68 | 3 / 2 | |
| 1.0.67 | 3 / 2 | |
| 1.0.66 | 3 / 2 | |
| 1.0.65 | 3 / 2 | |
| 1.0.64 | 3 / 2 | |
| 1.0.63 | 3 / 2 | |
| 1.0.62 | 3 / 2 | |
| 1.0.61 | 3 / 2 | |
| 1.0.60 | 3 / 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 / 1 | |
| 1.0.23 | 2 / 1 | |
| 1.0.22 | 2 / 1 | |
| 1.0.21 | 2 / 1 | |
| 1.0.20 | 2 / 1 | |
| 1.0.19 | 2 / 1 | |
| 1.0.18 | 2 / 1 | |
| 1.0.17 | 2 / 2 | |
| 1.0.16 | 2 / 2 | |
| 1.0.15 | 2 / 2 | |
| 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 | |
| 1.0.9 | 2 / 1 | |
| 1.0.8 | 2 / 1 | |
| 1.0.7 | 2 / 1 | |
| 1.0.6 | 2 / 1 | |
| 1.0.5 | 2 / 1 | |
| 1.0.4 | 2 / 1 | |
| 1.0.3 | 2 / 1 | |
| 1.0.2 | 2 / 1 | |
| 1.0.1 | 2 / 1 | |
| 1.0.0 | 2 / 1 |
v1.0.71
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.70
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.60
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.
v1.0.7
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.6
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.5
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.4
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.3
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.2
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.1
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.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.