@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.702 | 7 / 2 | |
| 1.0.701 | 7 / 2 | |
| 1.0.700 | 7 / 2 | |
| 1.0.699 | 7 / 2 | |
| 1.0.698 | 7 / 2 | |
| 1.0.697 | 7 / 2 | |
| 1.0.696 | 7 / 2 | |
| 1.0.695 | 7 / 2 | |
| 1.0.694 | 7 / 2 | |
| 1.0.693 | 7 / 2 | |
| 1.0.692 | 7 / 2 | |
| 1.0.691 | 7 / 2 | |
| 1.0.690 | 7 / 2 | |
| 1.0.689 | 7 / 2 | |
| 1.0.688 | 7 / 2 | |
| 1.0.687 | 7 / 2 | |
| 1.0.686 | 7 / 2 | |
| 1.0.685 | 7 / 2 | |
| 1.0.684 | 7 / 2 | |
| 1.0.683 | 7 / 2 | |
| 1.0.682 | 7 / 2 | |
| 1.0.677 | 7 / 2 | |
| 1.0.676 | 7 / 2 | |
| 1.0.675 | 7 / 2 | |
| 1.0.674 | 7 / 2 | |
| 1.0.673 | 7 / 2 | |
| 1.0.672 | 7 / 2 | |
| 1.0.671 | 7 / 2 | |
| 1.0.670 | 7 / 2 | |
| 1.0.669 | 7 / 2 | |
| 1.0.668 | 7 / 2 | |
| 1.0.667 | 7 / 2 | |
| 1.0.666 | 7 / 2 | |
| 1.0.665 | 7 / 2 | |
| 1.0.664 | 7 / 2 | |
| 1.0.663 | 7 / 2 | |
| 1.0.662 | 7 / 2 | |
| 1.0.661 | 7 / 2 | |
| 1.0.660 | 7 / 2 | |
| 1.0.659 | 7 / 2 | |
| 1.0.658 | 7 / 2 | |
| 1.0.657 | 7 / 2 | |
| 1.0.656 | 7 / 2 | |
| 1.0.655 | 7 / 2 | |
| 1.0.654 | 7 / 2 | |
| 1.0.653 | 7 / 2 | |
| 1.0.652 | 7 / 2 | |
| 1.0.651 | 7 / 2 | |
| 1.0.650 | 7 / 2 | |
| 1.0.649 | 7 / 2 | |
| 1.0.648 | 7 / 2 | |
| 1.0.647 | 7 / 2 | |
| 1.0.646 | 7 / 2 | |
| 1.0.645 | 7 / 2 | |
| 1.0.644 | 7 / 2 | |
| 1.0.643 | 7 / 2 | |
| 1.0.642 | 7 / 2 | |
| 1.0.641 | 7 / 2 | |
| 1.0.640 | 7 / 2 | |
| 1.0.639 | 7 / 2 | |
| 1.0.638 | 7 / 2 | |
| 1.0.637 | 7 / 2 | |
| 1.0.636 | 7 / 2 | |
| 1.0.635 | 7 / 2 | |
| 1.0.634 | 7 / 2 | |
| 1.0.633 | 7 / 2 | |
| 1.0.632 | 7 / 2 | |
| 1.0.631 | 7 / 2 | |
| 1.0.630 | 7 / 2 | |
| 1.0.629 | 7 / 2 | |
| 1.0.628 | 7 / 2 | |
| 1.0.627 | 7 / 2 | |
| 1.0.626 | 7 / 2 | |
| 1.0.625 | 7 / 2 | |
| 1.0.624 | 7 / 2 | |
| 1.0.623 | 7 / 2 | |
| 1.0.622 | 7 / 2 | |
| 1.0.621 | 7 / 2 | |
| 1.0.620 | 7 / 2 | |
| 1.0.619 | 7 / 2 | |
| 1.0.618 | 7 / 2 | |
| 1.0.617 | 7 / 2 | |
| 1.0.616 | 7 / 2 | |
| 1.0.615 | 7 / 2 | |
| 1.0.614 | 7 / 2 | |
| 1.0.613 | 7 / 2 | |
| 1.0.612 | 7 / 2 | |
| 1.0.611 | 7 / 2 | |
| 1.0.610 | 7 / 2 | |
| 1.0.609 | 7 / 2 | |
| 1.0.608 | 7 / 2 | |
| 1.0.607 | 7 / 2 | |
| 1.0.606 | 7 / 2 | |
| 1.0.605 | 7 / 2 | |
| 1.0.604 | 7 / 2 | |
| 1.0.603 | 7 / 2 | |
| 1.0.602 | 7 / 2 | |
| 1.0.601 | 7 / 2 | |
| 1.0.600 | 7 / 2 | |
| 1.0.599 | 7 / 2 |
v1.0.702
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.701
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.700
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.699
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.698
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.697
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.696
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.695
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.694
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.693
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.692
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.691
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.690
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.689
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.688
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.687
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.686
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.685
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.684
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.683
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.682
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.677
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.676
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.675
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.674
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.673
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.672
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.671
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.670
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.669
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.668
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.667
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.666
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.665
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.664
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.663
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.662
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.661
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.660
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.659
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.658
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.657
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.656
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.655
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.654
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.653
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.652
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.651
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.650
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.649
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.648
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.647
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.646
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.645
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.644
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.643
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.642
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.641
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.640
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.639
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.638
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.637
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.636
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.635
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.634
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.633
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.632
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.631
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.630
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.629
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.628
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.627
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.626
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.625
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.624
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.623
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.622
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.621
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.620
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.619
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.618
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.617
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.616
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.615
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.614
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.613
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.612
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.611
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.610
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.609
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.608
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.607
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.606
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.605
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.604
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.603
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.602
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.601
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.600
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.599
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.