← Home

@wix/auto_sdk_analytics-data_analytics-data

npm
22
Versions
MIT
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-wixyoungshinobiethanparielhwix-org-headlessitai.bendafalconciroir-wixdorchaouat

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
bogus-package bogus-package AI (bogus-package): Wix auto-generated SDK packages consistently lack descriptions/repo URLs; templated naming is intentional for this publisher. ai
npm-metadata no-description AI (npm-metadata): Stable pattern for Wix auto-generated SDK packages; not a malware indicator here. ai

Versions (showing 22 of 22)

Version Deps Published
1.0.21 3 / 2
1.0.20 3 / 2
1.0.19 3 / 2
1.0.18 3 / 2
1.0.17 2 / 2
1.0.16 2 / 2
1.0.15 2 / 2
1.0.14 2 / 2
1.0.13 2 / 2
1.0.12 2 / 2
1.0.11 2 / 2
1.0.10 2 / 2
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.5

1 finding
LOW No provenance attestation provenance

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

v1.0.4

1 finding
LOW No provenance attestation provenance

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

v1.0.3

2 findings
MEDIUM Publisher changed: wix-ci-publisher → roir-wix (on 2025-05-01, unremoved on npm for 443d) provenance

This version was published by a different npm account (roir-wix) than the most recent previously approved version (wix-ci-publisher) on 2025-05-01. It has since remained available on npm for 443 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.0.2

1 finding
LOW No provenance attestation provenance

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

v1.0.1

1 finding
LOW No provenance attestation provenance

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

v1.0.0

1 finding
LOW No provenance attestation provenance

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