← Home

@wix/auth-management

51
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-sessionsyurynixdimarysk-wixydanivamitde007youngshinobiethanpshlomitc-wixarielhwix-org-headlessfalconcinadavlacroir-wixdorchaouat

Keywords

wixSdkBackendModulewixSdkPageModulewixSdkPublicModule

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
bogus-package bogus-package AI (bogus-package): Auto-generated Wix SDK module; templated naming, no description, and no repo URL are expected patterns for this package family. ai
npm-metadata no-description AI (npm-metadata): Wix auto-generated SDK packages consistently omit descriptions; stable false positive for this package. ai
provenance no-provenance AI (provenance): Wix CI pipeline does not attach Sigstore provenance; consistent across all versions. ai

Versions (showing 51 of 55)

View all versions
Version Deps Published
1.0.88 1 / 2
1.0.87 1 / 2
1.0.86 1 / 2
1.0.85 1 / 2
1.0.84 1 / 2
1.0.83 1 / 2
1.0.82 1 / 2
1.0.81 1 / 2
1.0.80 1 / 2
1.0.79 1 / 2
1.0.78 1 / 2
1.0.77 1 / 2
1.0.74 1 / 2
1.0.73 1 / 2
1.0.72 1 / 2
1.0.71 1 / 2
1.0.70 1 / 2
1.0.69 1 / 2
1.0.68 1 / 2
1.0.67 1 / 2
1.0.66 1 / 2
1.0.65 1 / 2
1.0.64 1 / 2
1.0.63 1 / 2
1.0.62 1 / 2
1.0.61 1 / 2
1.0.60 1 / 2
1.0.59 1 / 1
1.0.58 1 / 1
1.0.57 1 / 1
1.0.56 1 / 1
1.0.55 1 / 1
1.0.54 1 / 1
1.0.53 1 / 1
1.0.52 1 / 1
1.0.51 1 / 1
1.0.50 1 / 1
1.0.49 1 / 1
1.0.48 1 / 1
1.0.47 1 / 1
1.0.46 1 / 1
1.0.45 1 / 1
1.0.44 1 / 1
1.0.43 1 / 1
1.0.42 1 / 1
1.0.41 1 / 1
1.0.40 1 / 4
1.0.39 1 / 4
1.0.38 1 / 4
1.0.37 1 / 4
1.0.36 1 / 4

v1.0.55

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.

v1.0.54

2 findings
INFO No provenance attestation provenance

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

INFO Publisher changed: roir-wix → wix-ci-publisher (on 2025-05-08, known maintainer) provenance

This version was published by a different npm account (wix-ci-publisher) than the most recent previously approved version (roir-wix) on 2025-05-08, but wix-ci-publisher is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.0.53

2 findings
MEDIUM Publisher changed: wix-ci-publisher → roir-wix (on 2025-04-29, unremoved on npm for 445d) provenance

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

INFO No provenance attestation provenance

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

v1.0.52

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.51

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.50

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.49

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.48

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.47

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.46

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.45

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.44

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.43

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.42

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.41

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.40

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.39

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.38

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.37

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.36

1 finding
INFO No provenance attestation provenance

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