← Home

@wix/admin

npm
5
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

yoavwix-cishahatawixnpmwix-ambassadornetanelgiladwix-ci-publisherwix-bi-publishergalil-teamlxgreenarikiliorgwixusability-sessionsyurynixoferb-wixdomasmakmayacoamitde007tombenezraitaytayhaimbrum-wixyoungshinobivarzagerbenblayer-wixitai.bendaarielhfalconciroir-wixdorchaouat

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
bogus-package bogus-package AI (bogus-package): Internal Wix org package; sparse metadata is expected for private SDK packages published via wix-ci-publisher. ai
phantom-deps phantom-dep:@wix/sdk AI (phantom-deps): Same org scope; likely re-exported or used indirectly via framework conventions. ai
phantom-deps phantom-dep:@babel/runtime AI (phantom-deps): Framework-scoped Babel runtime; loaded by convention in yoshi-flow-library builds. ai

Versions (showing 5 of 5)

Version Deps Published
1.6.1 3 / 8
1.6.0 3 / 8
1.5.0 3 / 8
1.4.0 3 / 8
1.3.0 3 / 8

v1.6.1

2 findings
HIGH Low-value / spam package indicators (4 signals, score 7) bogus-package

Matched 4 signal(s), weighted score 7: • [S_PUBLISHER_MASS_PRODUCTION] Maintainer 'oferb-wix' owns 63 packages, ≥70% share a templated name shape. • [S_README_NO_CODE] Short README with no code block, no install instructions, and no usage/API section. • [S_NO_REPO_NO_HOME] No repository, homepage, or bugs URL — genuine packages almost always link somewhere. • [S_NO_KEYWORDS] No keywords declared.

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.

v1.6.0

1 finding
LOW No provenance attestation provenance

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

v1.5.0

1 finding
LOW No provenance attestation provenance

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

v1.4.0

1 finding
LOW No provenance attestation provenance

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

v1.3.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.