@things-factory/sales-ui
UI module that handles sales order
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
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): Same org context; publisher track record supports legitimate transition. | ai | |
| provenance | publisher-changed | AI (provenance): wengliang95 is an established publisher in the @things-factory org with 431 approved packages; likely account rename from horwengliang95. | ai | |
| phantom-deps | phantom-dep:@things-factory/i18n-base | AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic fires on indirect/re-exported usage patterns common in this package family. | ai | |
| phantom-deps | phantom-dep:@things-factory/sales-base | AI (phantom-deps): Same-org scoped dep declared in package.json; phantom-dep heuristic is a stable false positive for this monorepo package. | ai |
Versions (showing 100 of 209)
| Version | Deps | Published |
|---|---|---|
| 4.3.650 | 9 / 0 | |
| 4.3.647 | 9 / 0 | |
| 4.3.646 | 9 / 0 | |
| 4.3.644 | 9 / 0 | |
| 4.3.643 | 9 / 0 | |
| 4.3.642 | 9 / 0 | |
| 4.3.639 | 9 / 0 | |
| 4.3.638 | 9 / 0 | |
| 4.3.637 | 9 / 0 | |
| 4.3.636 | 9 / 0 | |
| 4.3.635 | 9 / 0 | |
| 4.3.634 | 9 / 0 | |
| 4.3.632 | 9 / 0 | |
| 4.3.631 | 9 / 0 | |
| 4.3.629 | 9 / 0 | |
| 4.3.626 | 9 / 0 | |
| 4.3.625 | 9 / 0 | |
| 4.3.622 | 9 / 0 | |
| 4.3.621 | 9 / 0 | |
| 4.3.617 | 9 / 0 | |
| 4.3.616 | 9 / 0 | |
| 4.3.614 | 9 / 0 | |
| 4.3.609 | 9 / 0 | |
| 4.3.607 | 9 / 0 | |
| 4.3.605 | 9 / 0 | |
| 4.3.603 | 9 / 0 | |
| 4.3.602 | 9 / 0 | |
| 4.3.596 | 9 / 0 | |
| 4.3.595 | 9 / 0 | |
| 4.3.593 | 9 / 0 | |
| 4.3.591 | 9 / 0 | |
| 4.3.588 | 9 / 0 | |
| 4.3.587 | 9 / 0 | |
| 4.3.584 | 9 / 0 | |
| 4.3.583 | 9 / 0 | |
| 4.3.582 | 9 / 0 | |
| 4.3.581 | 9 / 0 | |
| 4.3.580 | 9 / 0 | |
| 4.3.579 | 9 / 0 | |
| 4.3.577 | 9 / 0 | |
| 4.3.576 | 9 / 0 | |
| 4.3.572 | 9 / 0 | |
| 4.3.567 | 9 / 0 | |
| 4.3.566 | 9 / 0 | |
| 4.3.563 | 9 / 0 | |
| 4.3.562 | 9 / 0 | |
| 4.3.561 | 9 / 0 | |
| 4.3.558 | 9 / 0 | |
| 4.3.554 | 9 / 0 | |
| 4.3.552 | 9 / 0 | |
| 4.3.551 | 9 / 0 | |
| 4.3.550 | 9 / 0 | |
| 4.3.549 | 9 / 0 | |
| 4.3.547 | 9 / 0 | |
| 4.3.546 | 9 / 0 | |
| 4.3.545 | 9 / 0 | |
| 4.3.544 | 9 / 0 | |
| 4.3.543 | 9 / 0 | |
| 4.3.542 | 9 / 0 | |
| 4.3.541 | 9 / 0 | |
| 4.3.539 | 9 / 0 | |
| 4.3.537 | 9 / 0 | |
| 4.3.536 | 9 / 0 | |
| 4.3.535 | 9 / 0 | |
| 4.3.534 | 9 / 0 | |
| 4.3.532 | 9 / 0 | |
| 4.3.531 | 9 / 0 | |
| 4.3.529 | 9 / 0 | |
| 4.3.527 | 9 / 0 | |
| 4.3.526 | 9 / 0 | |
| 4.3.525 | 9 / 0 | |
| 4.3.524 | 9 / 0 | |
| 4.3.523 | 9 / 0 | |
| 4.3.520 | 9 / 0 | |
| 4.3.518 | 9 / 0 | |
| 4.3.516 | 9 / 0 | |
| 4.3.515 | 9 / 0 | |
| 4.3.514 | 9 / 0 | |
| 4.3.513 | 9 / 0 | |
| 4.3.512 | 9 / 0 | |
| 4.3.511 | 9 / 0 | |
| 4.3.510 | 9 / 0 | |
| 4.3.509 | 9 / 0 | |
| 4.3.508 | 9 / 0 | |
| 4.3.505 | 9 / 0 | |
| 4.3.503 | 9 / 0 | |
| 4.3.502 | 9 / 0 | |
| 4.3.501 | 9 / 0 | |
| 4.3.500 | 9 / 0 | |
| 4.3.495 | 9 / 0 | |
| 4.3.494 | 9 / 0 | |
| 4.3.493 | 9 / 0 | |
| 4.3.492 | 9 / 0 | |
| 4.3.491 | 9 / 0 | |
| 4.3.490 | 9 / 0 | |
| 4.3.485 | 9 / 0 | |
| 4.3.482 | 9 / 0 | |
| 4.3.481 | 9 / 0 | |
| 4.3.479 | 9 / 0 | |
| 4.3.475 | 9 / 0 |
v4.3.626
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.625
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.622
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.621
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.617
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.616
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.614
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.609
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.607
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.605
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.603
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.602
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.596
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.595
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.593
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.591
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.588
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.587
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.584
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.583
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.582
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.581
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.580
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.579
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.577
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.576
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.572
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.567
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.566
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.563
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.562
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.561
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.558
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.554
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.552
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.551
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.550
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.549
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.547
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.546
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.545
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.544
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.543
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.542
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.541
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.539
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.537
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.536
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.535
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.534
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.532
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.531
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.529
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.527
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.526
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.525
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.524
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.523
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.520
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.518
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.516
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.515
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.514
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.513
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.512
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.511
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.510
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.509
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.508
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.505
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.503
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.502
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.501
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.500
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.495
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.494
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.493
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.492
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.491
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.490
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.485
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.482
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.481
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.479
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.475
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.