← Home

@wix/auto_sdk_calendar_participations

49
Versions
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

yoavwix-cishahatawixnpmwix-ambassadorwix-ci-publisherwix-bi-publishergalil-teamusability-sessionsyurynixydanivmayacoamitde007haimbrum-wixyoungshinobiethanpshlomitc-wixarielhwix-org-headlessfalconcinadavlacroir-wixdorchaouat

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:build/es/calendar-v3-participation-participations.universal-CRcW0LBD.d.mts AI (source-diff): Generated TypeScript declaration file with long lines; readable JSDoc content, not obfuscated code. ai
source-diff obfuscated-file:build/internal/es/calendar-v3-participation-participations.universal-jvGI_cFu.d.mts AI (source-diff): Generated TypeScript declaration file with long lines; readable JSDoc content, not obfuscated code. ai
source-diff obfuscated-file:build/cjs/calendar-v3-participation-participations.universal-CRcW0LBD.d.ts AI (source-diff): Generated TypeScript declaration file with long lines; readable JSDoc content, not obfuscated code. ai
source-diff obfuscated-file:build/internal/cjs/calendar-v3-participation-participations.universal-jvGI_cFu.d.ts AI (source-diff): Generated TypeScript declaration file with long lines; readable JSDoc content, not obfuscated code. ai
npm-metadata no-description AI (npm-metadata): Wix auto-SDK packages consistently omit descriptions; stable false positive for this publisher. ai
provenance no-provenance AI (provenance): Wix CI pipeline does not attach Sigstore provenance; consistent across all approved Wix SDK packages. ai
bogus-package bogus-package AI (bogus-package): Wix auto-generated SDK packages intentionally lack descriptions/repo URLs; templated naming is by design. ai

Versions (showing 49 of 49)

Version Deps Published
1.0.48 3 / 2
1.0.47 3 / 2
1.0.46 3 / 2
1.0.45 3 / 2
1.0.44 3 / 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.23 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 / 1
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 / 2
1.0.9 2 / 2
1.0.8 2 / 2
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.5

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.4

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.3

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.2

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.