@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 100 of 363)
| Version | Deps | Published |
|---|---|---|
| 1.0.1229 | 5 / 25 | |
| 1.0.1228 | 5 / 25 | |
| 1.0.1227 | 5 / 25 | |
| 1.0.1226 | 5 / 25 | |
| 1.0.1225 | 5 / 25 | |
| 1.0.1224 | 5 / 25 | |
| 1.0.1223 | 5 / 25 | |
| 1.0.1222 | 5 / 25 | |
| 1.0.1221 | 5 / 25 | |
| 1.0.1220 | 5 / 25 | |
| 1.0.1219 | 5 / 25 | |
| 1.0.1218 | 5 / 25 | |
| 1.0.1217 | 5 / 25 | |
| 1.0.1216 | 5 / 25 | |
| 1.0.1215 | 5 / 25 | |
| 1.0.1213 | 5 / 25 | |
| 1.0.1212 | 5 / 25 | |
| 1.0.1211 | 5 / 25 | |
| 1.0.1210 | 5 / 25 | |
| 1.0.1209 | 5 / 25 | |
| 1.0.1208 | 5 / 25 | |
| 1.0.1207 | 5 / 25 | |
| 1.0.1206 | 5 / 25 | |
| 1.0.1205 | 5 / 25 | |
| 1.0.1204 | 5 / 25 | |
| 1.0.1203 | 5 / 25 | |
| 1.0.1202 | 5 / 25 | |
| 1.0.1201 | 5 / 25 | |
| 1.0.1200 | 5 / 25 | |
| 1.0.1199 | 5 / 25 | |
| 1.0.1198 | 5 / 25 | |
| 1.0.1197 | 5 / 25 | |
| 1.0.1196 | 5 / 25 | |
| 1.0.1195 | 5 / 25 | |
| 1.0.1194 | 5 / 25 | |
| 1.0.1193 | 5 / 25 | |
| 1.0.1192 | 5 / 25 | |
| 1.0.1191 | 5 / 25 | |
| 1.0.1190 | 5 / 25 | |
| 1.0.1189 | 5 / 25 | |
| 1.0.1188 | 5 / 25 | |
| 1.0.1187 | 5 / 25 | |
| 1.0.1186 | 5 / 25 | |
| 1.0.1185 | 5 / 25 | |
| 1.0.1184 | 5 / 25 | |
| 1.0.1183 | 5 / 25 | |
| 1.0.1182 | 5 / 25 | |
| 1.0.1181 | 5 / 25 | |
| 1.0.1180 | 5 / 25 | |
| 1.0.1178 | 5 / 25 | |
| 1.0.1177 | 5 / 25 | |
| 1.0.1176 | 5 / 25 | |
| 1.0.1175 | 5 / 25 | |
| 1.0.1174 | 5 / 25 | |
| 1.0.1173 | 5 / 25 | |
| 1.0.1172 | 5 / 25 | |
| 1.0.1171 | 5 / 25 | |
| 1.0.1170 | 5 / 25 | |
| 1.0.1169 | 5 / 25 | |
| 1.0.1168 | 5 / 25 | |
| 1.0.1167 | 5 / 25 | |
| 1.0.1166 | 5 / 25 | |
| 1.0.1165 | 5 / 25 | |
| 1.0.1164 | 5 / 25 | |
| 1.0.1163 | 5 / 25 | |
| 1.0.1162 | 5 / 25 | |
| 1.0.1161 | 5 / 25 | |
| 1.0.1160 | 5 / 25 | |
| 1.0.1159 | 5 / 25 | |
| 1.0.1158 | 5 / 25 | |
| 1.0.1157 | 5 / 25 | |
| 1.0.1156 | 5 / 25 | |
| 1.0.1155 | 5 / 25 | |
| 1.0.1154 | 5 / 25 | |
| 1.0.1153 | 5 / 25 | |
| 1.0.1152 | 5 / 25 | |
| 1.0.1099 | 5 / 25 | |
| 1.0.1098 | 5 / 25 | |
| 1.0.1097 | 5 / 25 | |
| 1.0.1096 | 5 / 25 | |
| 1.0.1095 | 5 / 25 | |
| 1.0.1094 | 5 / 25 | |
| 1.0.1093 | 5 / 25 | |
| 1.0.1092 | 5 / 25 | |
| 1.0.1091 | 5 / 25 | |
| 1.0.1090 | 5 / 25 | |
| 1.0.1089 | 5 / 25 | |
| 1.0.1088 | 5 / 25 | |
| 1.0.1087 | 5 / 25 | |
| 1.0.1086 | 5 / 25 | |
| 1.0.1085 | 5 / 25 | |
| 1.0.1084 | 5 / 25 | |
| 1.0.1083 | 5 / 25 | |
| 1.0.1082 | 5 / 25 | |
| 1.0.1081 | 5 / 25 | |
| 1.0.1080 | 5 / 25 | |
| 1.0.1079 | 5 / 25 | |
| 1.0.1078 | 5 / 25 | |
| 1.0.1077 | 5 / 25 | |
| 1.0.1076 | 5 / 25 |
v1.0.1229
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1228
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1227
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1226
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1225
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1224
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1223
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1222
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1221
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1220
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1219
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1218
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1217
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1216
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1215
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1213
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1212
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1211
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1210
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1209
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1208
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1207
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1206
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1205
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1204
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1203
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1202
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1201
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1200
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1199
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1198
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1197
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1196
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1195
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1194
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1193
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1192
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1191
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1190
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1189
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1188
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1187
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1186
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1185
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1184
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1183
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1182
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1181
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1180
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1178
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1177
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1176
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1175
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1174
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1173
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1172
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1171
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1170
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1169
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1168
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1167
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1166
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1165
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1164
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1163
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1162
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1161
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1160
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1159
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1158
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1157
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1156
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1155
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1154
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1153
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1152
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1099
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1098
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1097
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1096
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1095
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1094
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1093
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1092
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1091
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1090
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1089
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1088
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1087
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1086
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1085
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1084
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1083
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1082
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1081
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1080
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1079
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1078
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1077
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1076
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.