@modern-js/bff-runtime
A Progressive React Framework for modern web development.
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 | no-provenance | AI (provenance): Large established monorepo package; lack of provenance is consistent across all versions. | ai | |
| dependencies | unvetted-dep:farrow-api | AI (dependencies): farrow-api is a documented BFF dependency of modern.js; stable across versions. | ai | |
| dependencies | unvetted-dep:farrow-schema | AI (dependencies): farrow-schema is a documented BFF dependency of modern.js; stable across versions. | ai | |
| dependencies | unvetted-dep:farrow-pipeline | AI (dependencies): farrow-pipeline is a documented BFF dependency of modern.js; stable across versions. | ai | |
| phantom-deps | phantom-dep:farrow-api | AI (phantom-deps): farrow-api is a declared runtime dep used indirectly via re-exports; phantom-dep heuristic is a false positive here. | ai | |
| phantom-deps | phantom-dep:@swc/helpers | AI (phantom-deps): Known implicit SWC runtime helper; not directly imported but required at runtime by compiled output. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package; minimal README is expected and not indicative of spam/phishing. | ai |
Versions (showing 35 of 35)
| Version | Deps | Published |
|---|---|---|
| 3.2.2 | 4 / 4 | |
| 3.2.1 | 4 / 4 | |
| 3.2.0 | 4 / 4 | |
| 3.1.5 | 4 / 4 | |
| 3.1.4 | 4 / 4 | |
| 3.1.3 | 4 / 4 | |
| 3.1.2 | 4 / 4 | |
| 3.1.1 | 4 / 4 | |
| 3.1.0 | 4 / 4 | |
| 3.0.5 | 4 / 4 | |
| 3.0.4 | 4 / 4 | |
| 3.0.3 | 4 / 4 | |
| 3.0.2 | 4 / 4 | |
| 3.0.1 | 4 / 4 | |
| 3.0.0 | 4 / 4 | |
| 2.71.0 | 4 / 7 | |
| 2.70.8 | 4 / 7 | |
| 2.70.7 | 4 / 7 | |
| 2.70.6 | 4 / 7 | |
| 2.70.5 | 4 / 7 | |
| 2.70.4 | 4 / 7 | |
| 2.70.3 | 4 / 7 | |
| 2.70.2 | 4 / 7 | |
| 2.70.1 | 4 / 7 | |
| 2.70.0 | 4 / 7 | |
| 2.69.7 | 4 / 7 | |
| 2.69.6 | 4 / 7 | |
| 2.69.5 | 4 / 7 | |
| 2.69.4 | 4 / 7 | |
| 2.69.3 | 4 / 7 | |
| 2.69.2 | 4 / 7 | |
| 2.69.1 | 4 / 7 | |
| 2.69.0 | 4 / 7 | |
| 2.68.20 | 4 / 7 | |
| 2.68.19 | 4 / 7 |
v3.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.71.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.70.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.70.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.70.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.70.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.70.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.70.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.70.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.70.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.70.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.69.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.69.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.69.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.69.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.69.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.69.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.69.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.69.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.68.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.68.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.