@flarehr/pba-benefits-admin
* `npm install`: Installs dependencies
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:goober | AI (phantom-deps): Referenced in babelMacros twin preset; required for build, not direct import. | ai | |
| phantom-deps | phantom-dep:preact | AI (phantom-deps): Build tool dependency; referenced in eslint config and build scripts. | ai | |
| phantom-deps | phantom-dep:preact-custom-element | AI (phantom-deps): Build tool dependency; referenced in devDeps and type definitions. | ai | |
| phantom-deps | phantom-dep:formik | AI (phantom-deps): Form library used implicitly; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): React DOM used implicitly; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:lucide-react | AI (phantom-deps): Icon library used implicitly in JSX; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:tailwind-merge | AI (phantom-deps): Utility used in config/runtime; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:clsx | AI (phantom-deps): Utility library used implicitly in JSX; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@vitejs/plugin-react | AI (phantom-deps): Vite plugin used in config; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@tanstack/react-table | AI (phantom-deps): Table library used implicitly; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:class-variance-authority | AI (phantom-deps): Utility used in config/runtime; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-dropdown-menu | AI (phantom-deps): UI component library used implicitly; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-slot | AI (phantom-deps): UI component library used implicitly; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:axios | AI (phantom-deps): HTTP client used in config/runtime; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:react | AI (phantom-deps): React used implicitly in JSX; stable pattern for this package. | ai |
Versions (showing 62 of 363)
| Version | Deps | Published |
|---|---|---|
| 1.0.1075 | 5 / 25 | |
| 1.0.1074 | 5 / 25 | |
| 1.0.1073 | 5 / 25 | |
| 1.0.1072 | 5 / 25 | |
| 1.0.1071 | 5 / 25 | |
| 1.0.1070 | 5 / 25 | |
| 1.0.1069 | 5 / 25 | |
| 1.0.1068 | 5 / 25 | |
| 1.0.1067 | 5 / 25 | |
| 1.0.1066 | 5 / 25 | |
| 1.0.1065 | 5 / 25 | |
| 1.0.1064 | 5 / 25 | |
| 1.0.1063 | 5 / 25 | |
| 1.0.1062 | 5 / 25 | |
| 1.0.1061 | 5 / 25 | |
| 1.0.1060 | 5 / 25 | |
| 1.0.1059 | 5 / 25 | |
| 1.0.1058 | 5 / 25 | |
| 1.0.1057 | 5 / 25 | |
| 1.0.1056 | 5 / 25 | |
| 1.0.1055 | 5 / 25 | |
| 1.0.1054 | 5 / 25 | |
| 1.0.1053 | 5 / 25 | |
| 1.0.1052 | 5 / 25 | |
| 1.0.1051 | 5 / 25 | |
| 1.0.1050 | 5 / 25 | |
| 1.0.1049 | 5 / 25 | |
| 1.0.1048 | 5 / 25 | |
| 1.0.1047 | 5 / 25 | |
| 1.0.1046 | 5 / 25 | |
| 1.0.1045 | 5 / 25 | |
| 1.0.1044 | 5 / 25 | |
| 1.0.1043 | 5 / 25 | |
| 1.0.1042 | 5 / 25 | |
| 1.0.1041 | 5 / 25 | |
| 1.0.1040 | 5 / 25 | |
| 1.0.1039 | 5 / 25 | |
| 1.0.1038 | 5 / 25 | |
| 1.0.1037 | 5 / 25 | |
| 1.0.1036 | 5 / 25 | |
| 1.0.1035 | 5 / 25 | |
| 1.0.1034 | 5 / 25 | |
| 1.0.1033 | 5 / 25 | |
| 1.0.1032 | 5 / 25 | |
| 1.0.1031 | 5 / 25 | |
| 1.0.1030 | 5 / 25 | |
| 1.0.1029 | 5 / 25 | |
| 1.0.1028 | 5 / 25 | |
| 1.0.1027 | 5 / 25 | |
| 1.0.1026 | 5 / 25 | |
| 1.0.1025 | 5 / 25 | |
| 1.0.1024 | 5 / 25 | |
| 1.0.1023 | 5 / 25 | |
| 1.0.1022 | 5 / 25 | |
| 1.0.1021 | 5 / 25 | |
| 1.0.1020 | 5 / 25 | |
| 1.0.1019 | 5 / 25 | |
| 1.0.1018 | 5 / 25 | |
| 1.0.1017 | 5 / 25 | |
| 1.0.1016 | 5 / 25 | |
| 1.0.1015 | 5 / 25 | |
| 1.0.1014 | 5 / 25 |
v1.0.1075
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1074
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1073
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1072
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1071
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1070
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1069
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1068
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1067
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1066
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1065
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1064
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1063
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1062
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1061
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1060
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1059
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1058
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1057
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1056
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1055
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1054
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1053
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1052
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1051
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1050
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1049
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1048
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1047
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1046
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1045
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1044
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1043
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1042
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1041
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1040
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1039
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1038
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1037
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1036
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1035
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1034
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1033
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1032
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1031
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1030
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1029
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1028
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1027
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1026
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1025
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1024
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1023
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1022
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1021
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1020
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1019
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1018
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1017
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1016
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1015
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1014
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.