@wix/auto_sdk_calendar_events
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/calendar-v3-event-events.universal-Cfq4Piiv.d.ts | AI (source-diff): Long-line TypeScript declaration file from Wix auto-SDK generation; not obfuscated code. | ai | |
| source-diff | obfuscated-file:build/calendar-v3-event-events.universal-Cfq4Piiv.d.ts | AI (source-diff): Long-line TypeScript declaration file from Wix auto-SDK generation; not obfuscated code. | ai | |
| source-diff | obfuscated-file:build/internal/calendar-v3-event-events.universal-Cfq4Piiv.d.mts | AI (source-diff): Long-line TypeScript declaration file from Wix auto-SDK generation; not obfuscated code. | ai | |
| source-diff | obfuscated-file:build/calendar-v3-event-events.universal-Cfq4Piiv.d.mts | AI (source-diff): Long-line TypeScript declaration file from Wix auto-SDK generation; not obfuscated code. | ai | |
| source-diff | obfuscated-file:build/internal/calendar-v3-event-events.universal-CLDnUCNu.d.mts | AI (source-diff): TypeScript declaration file with long lines from JSDoc; not obfuscated, pattern stable for Wix auto-SDK packages. | ai | |
| source-diff | obfuscated-file:build/internal/calendar-v3-event-events.universal-CLDnUCNu.d.ts | AI (source-diff): TypeScript declaration file with long lines from JSDoc; not obfuscated, pattern stable for Wix auto-SDK packages. | ai | |
| source-diff | obfuscated-file:build/calendar-v3-event-events.universal-CLDnUCNu.d.mts | AI (source-diff): TypeScript declaration file with long lines from JSDoc; not obfuscated, pattern stable for Wix auto-SDK packages. | ai | |
| source-diff | obfuscated-file:build/calendar-v3-event-events.universal-CLDnUCNu.d.ts | AI (source-diff): TypeScript declaration file with long lines from JSDoc; not obfuscated, pattern stable for Wix auto-SDK packages. | ai | |
| source-diff | obfuscated-file:build/cjs/calendar-v3-event-events.universal-CLDnUCNu.d.ts | AI (source-diff): TypeScript declaration file with long lines from dense JSDoc/type unions; not obfuscated code. | ai | |
| source-diff | obfuscated-file:build/es/calendar-v3-event-events.universal-CLDnUCNu.d.mts | AI (source-diff): TypeScript declaration file with long lines from dense JSDoc/type unions; not obfuscated code. | ai | |
| source-diff | obfuscated-file:build/internal/es/calendar-v3-event-events.universal-CLDnUCNu.d.mts | AI (source-diff): TypeScript declaration file with long lines from dense JSDoc/type unions; not obfuscated code. | ai | |
| source-diff | obfuscated-file:build/internal/cjs/calendar-v3-event-events.universal-CLDnUCNu.d.ts | AI (source-diff): TypeScript declaration file with long lines from dense JSDoc/type unions; 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 type unions; not obfuscated code. Stable pattern for this Wix auto-SDK package. | ai | |
| source-diff | obfuscated-file:build/internal/es/index.typings.d.mts | AI (source-diff): Same as above — generated .d.mts file with long type lines, not obfuscation. Stable for this package. | ai | |
| source-diff | obfuscated-file:build/internal/calendar-v3-event-events.universal-DwDyFLdW.d.ts | AI (source-diff): TypeScript declaration file with long lines from concatenated JSDoc/type definitions; not obfuscated code. | ai | |
| source-diff | obfuscated-file:build/calendar-v3-event-events.universal-DwDyFLdW.d.ts | AI (source-diff): TypeScript declaration file with long lines from concatenated JSDoc/type definitions; not obfuscated code. | ai | |
| source-diff | obfuscated-file:build/internal/calendar-v3-event-events.universal-DwDyFLdW.d.mts | AI (source-diff): TypeScript declaration file with long lines from concatenated JSDoc/type definitions; not obfuscated code. | ai | |
| source-diff | obfuscated-file:build/calendar-v3-event-events.universal-DwDyFLdW.d.mts | AI (source-diff): TypeScript declaration file with long lines from concatenated JSDoc/type definitions; not obfuscated code. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Wix auto-SDK packages consistently omit descriptions; stable false positive for this package family. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Wix auto-generated SDK package; templated naming, no description/keywords/repo are expected patterns for this family. | ai |
Versions (showing 51 of 76)
| Version | Deps | Published |
|---|---|---|
| 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 | 3 / 2 | |
| 1.0.80 | 3 / 2 | |
| 1.0.79 | 3 / 2 | |
| 1.0.78 | 3 / 2 | |
| 1.0.77 | 3 / 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 | |
| 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 |
v1.0.86
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.85
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.84
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.83
1 findingPackage 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. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.75
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.74
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.73
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.71
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.70
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.69
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.68
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.67
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.66
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.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
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.39
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.38
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.37
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.36
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.35
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.