@flarehr/superhero-pba-support-admin
A PBA app support admin tool which you can access from Superhero: https://test-partner.flarehr.com/superhero/#/benefits-app
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:uuid | AI (phantom-deps): Bundled frontend package; deps referenced in config/build rather than direct imports is expected pattern. | ai | |
| phantom-deps | phantom-dep:axios | AI (phantom-deps): Bundled frontend package; deps referenced in config/build rather than direct imports is expected pattern. | ai | |
| phantom-deps | phantom-dep:preact | AI (phantom-deps): Bundled frontend package; deps referenced in config/build rather than direct imports is expected pattern. | ai | |
| phantom-deps | phantom-dep:framer-motion | AI (phantom-deps): Bundled frontend package; deps referenced in config/build rather than direct imports is expected pattern. | ai | |
| phantom-deps | phantom-dep:@tailwindcss/forms | AI (phantom-deps): Bundled frontend package; deps referenced in config/build rather than direct imports is expected pattern. | ai | |
| phantom-deps | phantom-dep:preact-custom-element | AI (phantom-deps): Bundled frontend package; deps referenced in config/build rather than direct imports is expected pattern. | ai |
Versions (showing 100 of 354)
| Version | Deps | Published |
|---|---|---|
| 1.0.1394 | 6 / 23 | |
| 1.0.1393 | 6 / 23 | |
| 1.0.1392 | 6 / 23 | |
| 1.0.1391 | 6 / 23 | |
| 1.0.1390 | 6 / 23 | |
| 1.0.1389 | 6 / 23 | |
| 1.0.1388 | 6 / 23 | |
| 1.0.1387 | 6 / 23 | |
| 1.0.1386 | 6 / 23 | |
| 1.0.1385 | 6 / 23 | |
| 1.0.1384 | 6 / 23 | |
| 1.0.1383 | 6 / 23 | |
| 1.0.1382 | 6 / 23 | |
| 1.0.1381 | 6 / 23 | |
| 1.0.1380 | 6 / 23 | |
| 1.0.1379 | 6 / 23 | |
| 1.0.1378 | 6 / 23 | |
| 1.0.1377 | 6 / 23 | |
| 1.0.1376 | 6 / 23 | |
| 1.0.1375 | 6 / 23 | |
| 1.0.1374 | 6 / 23 | |
| 1.0.1373 | 6 / 23 | |
| 1.0.1372 | 6 / 23 | |
| 1.0.1371 | 6 / 23 | |
| 1.0.1370 | 6 / 23 | |
| 1.0.1369 | 6 / 23 | |
| 1.0.1368 | 6 / 23 | |
| 1.0.1367 | 6 / 23 | |
| 1.0.1366 | 6 / 23 | |
| 1.0.1364 | 6 / 23 | |
| 1.0.1363 | 6 / 23 | |
| 1.0.1360 | 6 / 23 | |
| 1.0.1359 | 6 / 23 | |
| 1.0.1358 | 6 / 23 | |
| 1.0.1357 | 6 / 23 | |
| 1.0.1356 | 6 / 23 | |
| 1.0.1355 | 6 / 23 | |
| 1.0.1354 | 6 / 23 | |
| 1.0.1352 | 6 / 23 | |
| 1.0.1351 | 6 / 23 | |
| 1.0.1350 | 6 / 23 | |
| 1.0.1349 | 6 / 23 | |
| 1.0.1348 | 6 / 23 | |
| 1.0.1347 | 6 / 23 | |
| 1.0.1345 | 6 / 23 | |
| 1.0.1344 | 6 / 23 | |
| 1.0.1343 | 6 / 23 | |
| 1.0.1342 | 6 / 23 | |
| 1.0.1341 | 6 / 23 | |
| 1.0.1340 | 6 / 23 | |
| 1.0.1337 | 6 / 23 | |
| 1.0.1336 | 6 / 23 | |
| 1.0.1334 | 6 / 23 | |
| 1.0.1332 | 6 / 23 | |
| 1.0.1269 | 6 / 23 | |
| 1.0.1268 | 6 / 23 | |
| 1.0.1267 | 6 / 23 | |
| 1.0.1266 | 6 / 23 | |
| 1.0.1265 | 6 / 23 | |
| 1.0.1264 | 6 / 23 | |
| 1.0.1263 | 6 / 23 | |
| 1.0.1262 | 6 / 23 | |
| 1.0.1261 | 6 / 23 | |
| 1.0.1260 | 6 / 23 | |
| 1.0.1259 | 6 / 23 | |
| 1.0.1258 | 6 / 23 | |
| 1.0.1257 | 6 / 23 | |
| 1.0.1256 | 6 / 23 | |
| 1.0.1255 | 6 / 23 | |
| 1.0.1254 | 6 / 23 | |
| 1.0.1253 | 6 / 23 | |
| 1.0.1252 | 6 / 23 | |
| 1.0.1251 | 6 / 23 | |
| 1.0.1250 | 6 / 23 | |
| 1.0.1249 | 6 / 23 | |
| 1.0.1248 | 6 / 23 | |
| 1.0.1247 | 6 / 23 | |
| 1.0.1246 | 6 / 23 | |
| 1.0.1245 | 6 / 23 | |
| 1.0.1244 | 6 / 23 | |
| 1.0.1243 | 6 / 23 | |
| 1.0.1242 | 6 / 23 | |
| 1.0.1241 | 6 / 23 | |
| 1.0.1240 | 6 / 23 | |
| 1.0.1239 | 6 / 23 | |
| 1.0.1238 | 6 / 23 | |
| 1.0.1237 | 6 / 23 | |
| 1.0.1236 | 6 / 23 | |
| 1.0.1235 | 6 / 23 | |
| 1.0.1234 | 6 / 23 | |
| 1.0.1233 | 6 / 23 | |
| 1.0.1232 | 6 / 23 | |
| 1.0.1231 | 6 / 23 | |
| 1.0.1230 | 6 / 23 | |
| 1.0.1229 | 6 / 23 | |
| 1.0.1228 | 6 / 23 | |
| 1.0.1227 | 6 / 23 | |
| 1.0.1226 | 6 / 23 | |
| 1.0.1225 | 6 / 23 | |
| 1.0.1224 | 6 / 23 |
v1.0.1394
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1393
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1392
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1391
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1390
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1389
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1388
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1387
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1386
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1385
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1384
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1383
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1382
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1381
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1380
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1379
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1378
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1377
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1376
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1375
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1374
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1373
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1372
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1371
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1370
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1369
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1368
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1367
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1366
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1364
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1363
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1360
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1359
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1358
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1357
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1356
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1355
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1354
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1352
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1351
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1350
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1349
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1348
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1347
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1345
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1344
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1343
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1342
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1341
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1340
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1337
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1336
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1334
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1332
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1269
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1268
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1267
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1266
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1265
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1264
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1263
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1262
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1261
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1260
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1259
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1258
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1257
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1256
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1255
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1254
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1253
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1252
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1251
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1250
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1249
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1248
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1247
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1246
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1245
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1244
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1243
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1242
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1241
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1240
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1239
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1238
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1237
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1236
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1235
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1234
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1233
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1232
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1231
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1230
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.