flux
An application architecture based on a unidirectional data flow
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Legitimate namespace transfer from unrelated 'flux' package to Facebook's Flux library; fisherwebdev (Bill Fisher) is the canonical Facebook maintainer. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): fisherwebdev is Bill Fisher, Facebook engineer and listed contributor; legitimate maintainer for Facebook's Flux. | ai | |
| source-diff | source-size-dropped | AI (source-diff): Complete package replacement: old flux (XML/HTML tool) → Facebook Flux (lightweight dispatcher). Size drop is expected. | ai | |
| provenance | missing-githead | AI (provenance): Flux is archived at facebookarchive; publish environment change is expected for maintenance releases on archived repos. | ai | |
| bogus-package | bogus-package | AI (bogus-package): The 'fb' maintainer is Facebook's official npm account, not a spam publisher. False positive. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Flux is a mature archived project; long gaps between publishes are normal maintenance cadence. | ai | |
| provenance | no-provenance | AI (provenance): Legacy Facebook package predates Sigstore provenance; no CI/CD pipeline expected for archived project. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 4.0.4 | 2 / 20 | |
| 4.0.3 | 2 / 19 | |
| 4.0.2 | 2 / 19 | |
| 4.0.1 | 2 / 19 | |
| 4.0.0 | 2 / 19 | |
| 3.1.3 | 2 / 20 | |
| 3.1.2 | 2 / 20 | |
| 3.1.1 | 2 / 20 | |
| 3.1.0 | 2 / 20 | |
| 3.0.0 | 2 / 20 | |
| 2.1.1 | 3 / 14 | |
| 2.1.0 | 3 / 14 | |
| 2.0.3 | 0 / 10 | |
| 2.0.1 | 0 / 6 | |
| 2.0.0 | 0 / 6 | |
| 1.0.2 | 3 / 1 | |
| 1.0.1 | 3 / 1 | |
| 1.0.0 | 3 / 1 |
v4.0.4
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: yangshun.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: yangshun.
v4.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
3 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: yangshun.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-12-15. This could indicate a legitimate maintainer transition or an account compromise.
v3.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
2 findingsThis version was published by a different npm account than previous versions on 2014-08-29. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.