@wix/analytics-session
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Wix internal team rotation via trusted CI publisher; not indicative of takeover. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Wix internal team rotation; combined with strong publisher track record, not a takeover signal. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Wix auto-generated SDK packages intentionally lack descriptions/repo URLs and share templated names; not spam. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Wix SDK autogen packages consistently omit descriptions; stable false positive for this package family. | ai |
Versions (showing 42 of 42)
| Version | Deps | Published |
|---|---|---|
| 1.0.41 | 1 / 2 | |
| 1.0.40 | 1 / 2 | |
| 1.0.39 | 1 / 2 | |
| 1.0.38 | 1 / 2 | |
| 1.0.37 | 1 / 2 | |
| 1.0.36 | 1 / 2 | |
| 1.0.35 | 1 / 2 | |
| 1.0.34 | 1 / 2 | |
| 1.0.33 | 1 / 2 | |
| 1.0.32 | 1 / 2 | |
| 1.0.31 | 1 / 2 | |
| 1.0.30 | 1 / 2 | |
| 1.0.29 | 1 / 2 | |
| 1.0.28 | 1 / 1 | |
| 1.0.27 | 1 / 1 | |
| 1.0.26 | 1 / 1 | |
| 1.0.25 | 1 / 1 | |
| 1.0.24 | 1 / 1 | |
| 1.0.23 | 1 / 1 | |
| 1.0.22 | 1 / 1 | |
| 1.0.21 | 1 / 1 | |
| 1.0.20 | 1 / 1 | |
| 1.0.19 | 1 / 4 | |
| 1.0.18 | 1 / 4 | |
| 1.0.17 | 1 / 4 | |
| 1.0.16 | 1 / 4 | |
| 1.0.15 | 1 / 4 | |
| 1.0.14 | 1 / 4 | |
| 1.0.13 | 1 / 4 | |
| 1.0.12 | 1 / 4 | |
| 1.0.11 | 1 / 4 | |
| 1.0.10 | 1 / 4 | |
| 1.0.9 | 1 / 4 | |
| 1.0.8 | 1 / 4 | |
| 1.0.7 | 1 / 4 | |
| 1.0.6 | 1 / 4 | |
| 1.0.5 | 1 / 4 | |
| 1.0.4 | 1 / 4 | |
| 1.0.3 | 1 / 4 | |
| 1.0.2 | 1 / 4 | |
| 1.0.1 | 1 / 4 | |
| 1.0.0 | 1 / 4 |
v1.0.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.