← Home

@wix/auto_sdk_data-resourceusage-service_data

npm
32
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-wixyoungshinobiethanpshlomitc-wixarielhwix-org-headlessfalconcinadavlacroir-wixdorchaouat

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-added AI (maintainer-change): Wix internal team rotation via CI publisher; consistent with org-level maintainer management. ai
maintainer-change maintainer-removed AI (maintainer-change): Same Wix internal rotation context; not indicative of takeover. ai
publish-pattern dormant-publish AI (publish-pattern): Auto-generated Wix SDK package; inactivity followed by update is normal for SDK versioning cadence. ai
bogus-package bogus-package AI (bogus-package): Wix auto-generated SDK packages are mass-produced with templated names and no metadata by design; not spam or malware. ai
npm-metadata no-description AI (npm-metadata): Wix auto-generated SDK packages consistently omit descriptions; stable false positive for this package family. ai

Versions (showing 32 of 32)

Version Deps Published
1.0.31 3 / 2
1.0.30 3 / 2
1.0.29 3 / 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 / 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 / 1
1.0.10 2 / 1
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.6

1 finding
LOW No provenance attestation provenance

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

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

1 finding
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.