@wix/crm
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Auto-generated Wix SDK packages consistently lack descriptions and repo URLs; this is a known pattern for this publisher. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Wix auto-generated SDK packages routinely omit descriptions; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@wix/auto_sdk_crm_notes | AI (dependencies): Internal Wix sub-package from a trusted publisher with 1583 approved packages. | ai | |
| dependencies | unvetted-dep:@wix/auto_sdk_crm_tasks | AI (dependencies): Internal Wix sub-package from a trusted publisher with 1583 approved packages. | ai | |
| dependencies | unvetted-dep:@wix/crm_app-extensions | AI (dependencies): Internal Wix sub-package from a trusted publisher with 1583 approved packages. | ai | |
| dependencies | unvetted-dep:@wix/auto_sdk_crm_labels | AI (dependencies): Internal Wix sub-package from a trusted publisher with 1583 approved packages. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): @wix/crm is a legitimate Wix CRM SDK, not a typosquat of 'cors'; the levenshtein match is a false positive. | ai | |
| dependencies | unvetted-dep:@wix/auto_sdk_crm_attachments | AI (dependencies): Internal Wix sub-package from a trusted publisher with 1583 approved packages. | ai | |
| dependencies | unvetted-dep:@wix/auto_sdk_crm_extended-fields | AI (dependencies): Internal Wix sub-package from a trusted publisher with 1583 approved packages. | ai | |
| dependencies | unvetted-dep:@wix/auto_sdk_crm_submitted-contact | AI (dependencies): Internal Wix sub-package from a trusted publisher with 1583 approved packages. | ai | |
| dependencies | unvetted-dep:@wix/auto_sdk_crm_pipelines | AI (dependencies): Internal Wix sub-package from a trusted publisher with 1583 approved packages. | ai | |
| dependencies | unvetted-dep:@wix/auto_sdk_crm_cards | AI (dependencies): Internal Wix sub-package from a trusted publisher with 1583 approved packages. | ai |
Versions (showing 100 of 901)
| Version | Deps | Published |
|---|---|---|
| 1.0.802 | 8 / 2 | |
| 1.0.801 | 8 / 2 | |
| 1.0.800 | 7 / 2 | |
| 1.0.799 | 7 / 2 | |
| 1.0.798 | 7 / 2 | |
| 1.0.797 | 7 / 2 | |
| 1.0.796 | 7 / 2 | |
| 1.0.795 | 7 / 2 | |
| 1.0.794 | 7 / 2 | |
| 1.0.793 | 7 / 2 | |
| 1.0.792 | 7 / 2 | |
| 1.0.791 | 7 / 2 | |
| 1.0.790 | 7 / 2 | |
| 1.0.789 | 7 / 2 | |
| 1.0.788 | 7 / 2 | |
| 1.0.787 | 7 / 2 | |
| 1.0.786 | 7 / 2 | |
| 1.0.785 | 7 / 2 | |
| 1.0.784 | 7 / 2 | |
| 1.0.783 | 7 / 2 | |
| 1.0.782 | 7 / 2 | |
| 1.0.781 | 7 / 2 | |
| 1.0.780 | 7 / 2 | |
| 1.0.779 | 7 / 2 | |
| 1.0.778 | 7 / 2 | |
| 1.0.777 | 7 / 2 | |
| 1.0.776 | 7 / 2 | |
| 1.0.775 | 7 / 2 | |
| 1.0.774 | 7 / 2 | |
| 1.0.773 | 7 / 2 | |
| 1.0.772 | 7 / 2 | |
| 1.0.771 | 7 / 2 | |
| 1.0.770 | 7 / 2 | |
| 1.0.769 | 7 / 2 | |
| 1.0.768 | 7 / 2 | |
| 1.0.767 | 7 / 2 | |
| 1.0.766 | 7 / 2 | |
| 1.0.765 | 7 / 2 | |
| 1.0.764 | 7 / 2 | |
| 1.0.763 | 7 / 2 | |
| 1.0.762 | 7 / 2 | |
| 1.0.761 | 7 / 2 | |
| 1.0.760 | 7 / 2 | |
| 1.0.759 | 7 / 2 | |
| 1.0.758 | 7 / 2 | |
| 1.0.757 | 7 / 2 | |
| 1.0.756 | 7 / 2 | |
| 1.0.755 | 7 / 2 | |
| 1.0.754 | 7 / 2 | |
| 1.0.753 | 7 / 2 | |
| 1.0.752 | 7 / 2 | |
| 1.0.751 | 7 / 2 | |
| 1.0.750 | 7 / 2 | |
| 1.0.749 | 7 / 2 | |
| 1.0.748 | 7 / 2 | |
| 1.0.747 | 7 / 2 | |
| 1.0.746 | 7 / 2 | |
| 1.0.745 | 7 / 2 | |
| 1.0.744 | 7 / 2 | |
| 1.0.743 | 7 / 2 | |
| 1.0.742 | 7 / 2 | |
| 1.0.741 | 7 / 2 | |
| 1.0.740 | 7 / 2 | |
| 1.0.739 | 7 / 2 | |
| 1.0.738 | 7 / 2 | |
| 1.0.737 | 7 / 2 | |
| 1.0.736 | 7 / 2 | |
| 1.0.735 | 7 / 2 | |
| 1.0.734 | 7 / 2 | |
| 1.0.733 | 7 / 2 | |
| 1.0.732 | 7 / 2 | |
| 1.0.731 | 7 / 2 | |
| 1.0.730 | 7 / 2 | |
| 1.0.729 | 7 / 2 | |
| 1.0.728 | 7 / 2 | |
| 1.0.727 | 7 / 2 | |
| 1.0.726 | 7 / 2 | |
| 1.0.725 | 7 / 2 | |
| 1.0.724 | 7 / 2 | |
| 1.0.723 | 7 / 2 | |
| 1.0.722 | 7 / 2 | |
| 1.0.721 | 7 / 2 | |
| 1.0.720 | 7 / 2 | |
| 1.0.719 | 7 / 2 | |
| 1.0.718 | 7 / 2 | |
| 1.0.717 | 7 / 2 | |
| 1.0.716 | 7 / 2 | |
| 1.0.715 | 7 / 2 | |
| 1.0.714 | 7 / 2 | |
| 1.0.713 | 7 / 2 | |
| 1.0.712 | 7 / 2 | |
| 1.0.711 | 7 / 2 | |
| 1.0.710 | 7 / 2 | |
| 1.0.709 | 7 / 2 | |
| 1.0.708 | 7 / 2 | |
| 1.0.707 | 7 / 2 | |
| 1.0.706 | 7 / 2 | |
| 1.0.705 | 7 / 2 | |
| 1.0.704 | 7 / 2 | |
| 1.0.703 | 7 / 2 |
v1.0.802
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.801
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.800
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.799
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.798
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.797
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.796
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.795
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.794
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.793
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.792
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.791
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.790
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.789
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.788
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.787
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.786
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.785
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.784
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.783
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.782
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.781
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.780
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.779
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.778
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.777
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.776
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.775
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.774
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.773
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.772
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.771
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.770
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.769
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.768
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.767
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.766
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.765
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.764
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.763
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.762
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.761
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.760
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.759
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.758
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.757
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.756
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.755
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.754
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.753
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.752
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.751
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.750
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.749
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.748
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.747
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.746
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.745
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.744
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.743
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.742
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.741
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.740
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.739
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.738
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.737
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.736
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.735
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.734
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.733
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.732
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.731
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.730
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.729
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.728
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.727
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.726
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.725
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.724
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.723
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.722
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.721
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.720
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.719
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.718
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.717
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.716
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.715
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.714
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.713
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.712
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.711
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.710
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.709
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.708
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.707
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.706
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.705
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.704
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.703
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.