@wix/auto_sdk_ecom_subscription-contracts
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/index.d.mts | AI (source-diff): Same pattern as above; auto-generated .d.mts with large re-export list. | ai | |
| source-diff | obfuscated-file:build/es/index.d.mts | AI (source-diff): Long-line TypeScript declaration file with large re-export list; standard Wix auto-generated SDK pattern. | ai | |
| source-diff | obfuscated-file:build/cjs/ecom-subscription-contracts-v1-subscription-contract-subscription-contracts.universal-BwexlKIz.d.ts | AI (source-diff): TypeScript declaration file with long lines from bundled types, not obfuscation. Stable pattern for Wix auto-SDK packages. | ai | |
| source-diff | obfuscated-file:build/internal/es/ecom-subscription-contracts-v1-subscription-contract-subscription-contracts.universal-DaM0yN7N.d.mts | AI (source-diff): TypeScript declaration file with long lines from bundled types, not obfuscation. Stable pattern for Wix auto-SDK packages. | ai | |
| source-diff | obfuscated-file:build/es/ecom-subscription-contracts-v1-subscription-contract-subscription-contracts.universal-BwexlKIz.d.mts | AI (source-diff): TypeScript declaration file with long lines from bundled types, not obfuscation. Stable pattern for Wix auto-SDK packages. | ai | |
| source-diff | obfuscated-file:build/internal/cjs/ecom-subscription-contracts-v1-subscription-contract-subscription-contracts.universal-DaM0yN7N.d.ts | AI (source-diff): TypeScript declaration file with long lines from bundled types, not obfuscation. Stable pattern for Wix auto-SDK packages. | ai | |
| source-diff | obfuscated-file:build/internal/es/meta.d.mts | AI (source-diff): TypeScript declaration file with long import lines; not obfuscated code. | ai | |
| source-diff | obfuscated-file:build/es/meta.d.mts | AI (source-diff): TypeScript declaration file with long import lines; not obfuscated code. | ai | |
| source-diff | obfuscated-file:build/es/index.typings.d.mts | AI (source-diff): TypeScript declaration file with long lines from verbose JSDoc; not obfuscated. Stable pattern for this auto-generated Wix SDK package. | ai | |
| source-diff | obfuscated-file:build/internal/es/index.typings.d.mts | AI (source-diff): Same pattern as above — JSDoc-heavy .d.mts file, not obfuscated. Stable for this package. | ai | |
| source-diff | obfuscated-file:build/internal/ecom-subscription-contracts-v1-subscription-contract-subscription-contracts.universal-DaM0yN7N.d.ts | AI (source-diff): Generated TypeScript declaration file with long lines; not executable code. Stable pattern for Wix auto-SDK packages. | ai | |
| source-diff | obfuscated-file:build/ecom-subscription-contracts-v1-subscription-contract-subscription-contracts.universal-BwexlKIz.d.ts | AI (source-diff): Generated TypeScript declaration file with long lines; not executable code. Stable pattern for Wix auto-SDK packages. | ai | |
| source-diff | obfuscated-file:build/internal/ecom-subscription-contracts-v1-subscription-contract-subscription-contracts.universal-DaM0yN7N.d.mts | AI (source-diff): Generated TypeScript declaration file with long lines; not executable code. Stable pattern for Wix auto-SDK packages. | ai | |
| source-diff | obfuscated-file:build/ecom-subscription-contracts-v1-subscription-contract-subscription-contracts.universal-BwexlKIz.d.mts | AI (source-diff): Generated TypeScript declaration file with long lines; not executable code. Stable pattern for Wix auto-SDK packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Wix auto-generated SDK packages intentionally lack descriptions, repos, and keywords — stable false positive for this package family. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Wix auto-generated SDK; missing description is by design across the entire package family. | ai |
Versions (showing 51 of 94)
| Version | Deps | Published |
|---|---|---|
| 1.0.115 | 3 / 2 | |
| 1.0.114 | 3 / 2 | |
| 1.0.113 | 3 / 2 | |
| 1.0.112 | 3 / 2 | |
| 1.0.111 | 3 / 2 | |
| 1.0.110 | 3 / 2 | |
| 1.0.109 | 3 / 2 | |
| 1.0.108 | 3 / 2 | |
| 1.0.107 | 3 / 2 | |
| 1.0.106 | 3 / 2 | |
| 1.0.105 | 2 / 2 | |
| 1.0.104 | 2 / 2 | |
| 1.0.103 | 2 / 2 | |
| 1.0.102 | 2 / 2 | |
| 1.0.101 | 2 / 2 | |
| 1.0.100 | 2 / 2 | |
| 1.0.99 | 2 / 2 | |
| 1.0.98 | 2 / 2 | |
| 1.0.97 | 2 / 2 | |
| 1.0.96 | 2 / 2 | |
| 1.0.95 | 2 / 2 | |
| 1.0.94 | 2 / 2 | |
| 1.0.93 | 2 / 2 | |
| 1.0.92 | 2 / 2 | |
| 1.0.91 | 2 / 2 | |
| 1.0.90 | 2 / 2 | |
| 1.0.89 | 2 / 2 | |
| 1.0.88 | 2 / 2 | |
| 1.0.87 | 2 / 2 | |
| 1.0.86 | 2 / 2 | |
| 1.0.85 | 2 / 2 | |
| 1.0.84 | 2 / 2 | |
| 1.0.83 | 2 / 2 | |
| 1.0.82 | 2 / 2 | |
| 1.0.81 | 2 / 2 | |
| 1.0.80 | 2 / 2 | |
| 1.0.79 | 2 / 2 | |
| 1.0.78 | 2 / 2 | |
| 1.0.77 | 2 / 2 | |
| 1.0.76 | 2 / 2 | |
| 1.0.75 | 2 / 2 | |
| 1.0.74 | 2 / 2 | |
| 1.0.73 | 2 / 2 | |
| 1.0.72 | 2 / 2 | |
| 1.0.71 | 2 / 2 | |
| 1.0.70 | 2 / 2 | |
| 1.0.69 | 2 / 2 | |
| 1.0.68 | 2 / 2 | |
| 1.0.67 | 2 / 2 | |
| 1.0.66 | 2 / 2 | |
| 1.0.65 | 2 / 2 |
v1.0.115
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.114
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.113
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.112
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.111
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.110
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.109
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.108
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.107
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.106
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.105
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.104
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.103
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.102
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.101
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.100
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.99
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.98
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.97
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.96
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.95
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.94
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.93
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.92
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.91
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.90
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.89
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.88
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.87
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.86
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.85
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.84
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.83
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.82
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.81
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.80
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.79
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.78
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.77
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.76
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.75
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.74
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.73
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.72
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.71
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.70
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.69
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.68
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.67
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.66
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.65
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.