@flarehr/superhero-fasttrack-middleware
Flare Superhero FastTrack Middleware Component
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:react | AI (phantom-deps): React is a peer dep referenced in config files; not directly imported in library code is expected. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): react-dom is a peer dep referenced in config; stable false positive for this component library. | ai | |
| phantom-deps | phantom-dep:@headlessui/react | AI (phantom-deps): UI component dep referenced in config; phantom-dep false positive for this package. | ai | |
| phantom-deps | phantom-dep:react-to-webcomponent | AI (phantom-deps): Referenced in config; stable false positive for this webcomponent wrapper package. | ai | |
| phantom-deps | phantom-dep:use-sync-external-store | AI (phantom-deps): React state utility dep referenced in config; stable false positive for this package. | ai | |
| install-scripts | install-script:postinstall | AI (install-scripts): dotnet tool restore is standard Fable/F# toolchain setup; consistent with the package's documented build pipeline across all versions. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.1.2463 | 5 / 6 | |
| 0.1.2445 | 5 / 6 | |
| 0.1.2444 | 5 / 6 | |
| 0.1.2416 | 5 / 6 | |
| 0.1.2415 | 5 / 6 | |
| 0.1.2414 | 5 / 6 |
v0.1.2463
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2445
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2416
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2415
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2414
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.