@flarehr/salpac-finops-admin
Salpac FinOps Admin
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:preact | AI (phantom-deps): Bundled Preact web component; deps declared for consumers, not directly imported in analyzed source. | ai | |
| phantom-deps | phantom-dep:@emotion/css | AI (phantom-deps): Emotion CSS-in-JS used via babel macros/config, not direct import; stable FP for this package. | ai | |
| phantom-deps | phantom-dep:@emotion/cache | AI (phantom-deps): Same as @emotion/css — macro-based usage pattern. | ai | |
| phantom-deps | phantom-dep:@emotion/react | AI (phantom-deps): Same as @emotion/css — macro-based usage pattern. | ai | |
| phantom-deps | phantom-dep:@emotion/styled | AI (phantom-deps): Same as @emotion/css — macro-based usage pattern. | ai | |
| phantom-deps | phantom-dep:react-hook-form | AI (phantom-deps): Peer dep for consumers of the web component; stable FP for this package. | ai | |
| phantom-deps | phantom-dep:@heroicons/react | AI (phantom-deps): Icon library used via JSX transform; stable FP for this package. | ai | |
| phantom-deps | phantom-dep:@headlessui/react | AI (phantom-deps): UI component lib used via JSX; stable FP for this package. | ai | |
| phantom-deps | phantom-dep:preact-custom-element | AI (phantom-deps): Used in build config/entry point; stable FP for this package. | ai |
Versions (showing 100 of 440)
| Version | Deps | Published |
|---|---|---|
| 1.0.787 | 9 / 32 | |
| 1.0.786 | 9 / 32 | |
| 1.0.785 | 9 / 32 | |
| 1.0.784 | 9 / 32 | |
| 1.0.783 | 9 / 32 | |
| 1.0.782 | 9 / 32 | |
| 1.0.781 | 9 / 32 | |
| 1.0.780 | 9 / 32 | |
| 1.0.779 | 9 / 32 | |
| 1.0.778 | 9 / 32 | |
| 1.0.777 | 9 / 32 | |
| 1.0.776 | 9 / 32 | |
| 1.0.775 | 9 / 32 | |
| 1.0.774 | 9 / 32 | |
| 1.0.773 | 9 / 32 | |
| 1.0.772 | 9 / 32 | |
| 1.0.771 | 9 / 32 | |
| 1.0.770 | 9 / 32 | |
| 1.0.769 | 9 / 32 | |
| 1.0.768 | 9 / 32 | |
| 1.0.767 | 9 / 32 | |
| 1.0.766 | 9 / 32 | |
| 1.0.765 | 9 / 32 | |
| 1.0.764 | 9 / 32 | |
| 1.0.763 | 9 / 32 | |
| 1.0.762 | 9 / 32 | |
| 1.0.761 | 9 / 32 | |
| 1.0.760 | 9 / 32 | |
| 1.0.759 | 9 / 32 | |
| 1.0.758 | 9 / 32 | |
| 1.0.757 | 9 / 32 | |
| 1.0.756 | 9 / 32 | |
| 1.0.755 | 9 / 32 | |
| 1.0.754 | 9 / 32 | |
| 1.0.753 | 9 / 32 | |
| 1.0.752 | 9 / 32 | |
| 1.0.751 | 9 / 32 | |
| 1.0.750 | 9 / 32 | |
| 1.0.749 | 9 / 32 | |
| 1.0.748 | 9 / 32 | |
| 1.0.747 | 9 / 32 | |
| 1.0.746 | 9 / 32 | |
| 1.0.745 | 9 / 32 | |
| 1.0.744 | 9 / 32 | |
| 1.0.743 | 9 / 32 | |
| 1.0.742 | 9 / 32 | |
| 1.0.741 | 9 / 32 | |
| 1.0.740 | 9 / 32 | |
| 1.0.739 | 9 / 32 | |
| 1.0.738 | 9 / 32 | |
| 1.0.737 | 9 / 32 | |
| 1.0.736 | 9 / 32 | |
| 1.0.735 | 9 / 32 | |
| 1.0.734 | 9 / 32 | |
| 1.0.733 | 9 / 32 | |
| 1.0.732 | 9 / 32 | |
| 1.0.731 | 9 / 32 | |
| 1.0.730 | 9 / 32 | |
| 1.0.729 | 9 / 32 | |
| 1.0.728 | 9 / 32 | |
| 1.0.727 | 9 / 32 | |
| 1.0.726 | 9 / 32 | |
| 1.0.725 | 9 / 32 | |
| 1.0.724 | 9 / 32 | |
| 1.0.723 | 9 / 32 | |
| 1.0.722 | 9 / 32 | |
| 1.0.721 | 9 / 32 | |
| 1.0.720 | 9 / 32 | |
| 1.0.719 | 9 / 32 | |
| 1.0.718 | 9 / 32 | |
| 1.0.717 | 9 / 32 | |
| 1.0.716 | 9 / 32 | |
| 1.0.715 | 9 / 32 | |
| 1.0.714 | 9 / 32 | |
| 1.0.713 | 9 / 32 | |
| 1.0.712 | 9 / 32 | |
| 1.0.711 | 9 / 32 | |
| 1.0.710 | 9 / 32 | |
| 1.0.709 | 9 / 32 | |
| 1.0.708 | 9 / 32 | |
| 1.0.707 | 9 / 32 | |
| 1.0.706 | 9 / 32 | |
| 1.0.705 | 9 / 32 | |
| 1.0.704 | 9 / 32 | |
| 1.0.703 | 9 / 32 | |
| 1.0.702 | 9 / 32 | |
| 1.0.701 | 9 / 32 | |
| 1.0.700 | 9 / 32 | |
| 1.0.699 | 9 / 32 | |
| 1.0.698 | 9 / 32 | |
| 1.0.697 | 9 / 32 | |
| 1.0.696 | 9 / 32 | |
| 1.0.695 | 9 / 32 | |
| 1.0.694 | 9 / 32 | |
| 1.0.693 | 9 / 32 | |
| 1.0.692 | 9 / 32 | |
| 1.0.691 | 9 / 32 | |
| 1.0.690 | 9 / 32 | |
| 1.0.689 | 9 / 32 | |
| 1.0.688 | 9 / 32 |
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.
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.