@flarehr/superhero-benefits-onboarding MIT 43 versions

@flarehr/superhero-benefits-onboarding

npm

Flare Superhero Benefits Onboarding Component

43

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

kyryll-flarehriain.fergusoningerweinberger74boris.etingof.flareflare.buildvitaly.brusentsevrubindershanganesan

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:axios	AI (phantom-deps): Bundled component; deps consumed at build time and shipped in dist/, not imported directly by static analysis.	ai	2026/04/29
phantom-deps	phantom-dep:preact	AI (phantom-deps): Same bundled-component pattern; stable false positive for this package.	ai	2026/04/29
phantom-deps	phantom-dep:jwt-decode	AI (phantom-deps): Same bundled-component pattern; stable false positive for this package.	ai	2026/04/29
phantom-deps	phantom-dep:fast-deep-equal	AI (phantom-deps): Same bundled-component pattern; stable false positive for this package.	ai	2026/04/29
phantom-deps	phantom-dep:@heroicons/react	AI (phantom-deps): Same bundled-component pattern; stable false positive for this package.	ai	2026/04/29
phantom-deps	phantom-dep:@headlessui/react	AI (phantom-deps): Same bundled-component pattern; stable false positive for this package.	ai	2026/04/29
phantom-deps	phantom-dep:preact-custom-element	AI (phantom-deps): Same bundled-component pattern; stable false positive for this package.	ai	2026/04/29

Versions (showing 43 of 346)

Version	Deps	Published
0.2.823	7 / 25	2025-06-09
0.2.822	7 / 25	2025-06-08
0.2.821	7 / 25	2025-06-07
0.2.820	7 / 25	2025-06-06
0.2.819	7 / 25	2025-06-05
0.2.818	7 / 25	2025-06-04
0.2.817	7 / 25	2025-06-03
0.2.816	7 / 25	2025-06-02
0.2.815	7 / 25	2025-06-01
0.2.814	7 / 25	2025-05-31
0.2.813	7 / 25	2025-05-30
0.2.812	7 / 25	2025-05-29
0.2.811	7 / 25	2025-05-28
0.2.810	7 / 25	2025-05-27
0.2.809	7 / 25	2025-05-26
0.2.808	7 / 25	2025-05-25
0.2.807	7 / 25	2025-05-24
0.2.806	7 / 25	2025-05-23
0.2.805	7 / 25	2025-05-22
0.2.804	7 / 25	2025-05-21
0.2.803	7 / 25	2025-05-20
0.2.802	7 / 25	2025-05-19
0.2.801	7 / 25	2025-05-18
0.2.800	7 / 25	2025-05-17
0.2.799	7 / 25	2025-05-16
0.2.798	7 / 25	2025-05-15
0.2.797	7 / 25	2025-05-14
0.2.796	7 / 25	2025-05-13
0.2.795	7 / 25	2025-05-12
0.2.794	7 / 25	2025-05-11
0.2.793	7 / 25	2025-05-10
0.2.792	7 / 25	2025-05-09
0.2.791	7 / 25	2025-05-08
0.2.790	7 / 25	2025-05-07
0.2.789	7 / 25	2025-05-06
0.2.788	7 / 25	2025-05-05
0.2.787	7 / 25	2025-05-04
0.2.786	7 / 25	2025-05-03
0.2.785	7 / 25	2025-05-02
0.2.784	7 / 25	2025-05-01
0.2.783	7 / 25	2025-04-30
0.2.782	7 / 25	2025-04-29
0.2.781	7 / 25	2025-04-28

v0.2.823

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.822

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.821

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.820

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.819

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.818

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.817

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.816

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.815

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.814

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.813

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.812

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.811

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.810

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.809

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.808

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.807

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.806

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.805

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.804

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.803

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.802

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.801

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.800

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.799

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.798

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.797

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.796

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.795

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.794

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.793

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.792

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.791

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.790

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.789

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.788

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.787

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.786

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.785

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.784

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.783

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.782

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.781

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.