@modern-js/bff-core
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:type-fest | AI (phantom-deps): type-fest is a legitimate utility dependency; phantom-dep heuristic doesn't account for config-file references. | ai | |
| phantom-deps | phantom-dep:@swc/helpers | AI (phantom-deps): Known implicit runtime dependency for SWC transpilation; stable pattern for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Framework package with legitimate repo; README structure matches Modern.js monorepo docs, not phishing. | ai |
Versions (showing 35 of 35)
| Version | Deps | Published |
|---|---|---|
| 3.2.2 | 5 / 10 | |
| 3.2.1 | 5 / 10 | |
| 3.2.0 | 5 / 10 | |
| 3.1.5 | 5 / 10 | |
| 3.1.4 | 5 / 10 | |
| 3.1.3 | 5 / 10 | |
| 3.1.2 | 5 / 10 | |
| 3.1.1 | 5 / 10 | |
| 3.1.0 | 5 / 10 | |
| 3.0.5 | 5 / 10 | |
| 3.0.4 | 5 / 10 | |
| 3.0.3 | 5 / 10 | |
| 3.0.2 | 5 / 10 | |
| 3.0.1 | 5 / 10 | |
| 3.0.0 | 5 / 10 | |
| 2.71.0 | 5 / 11 | |
| 2.70.8 | 5 / 11 | |
| 2.70.7 | 5 / 11 | |
| 2.70.6 | 5 / 11 | |
| 2.70.5 | 5 / 11 | |
| 2.70.4 | 5 / 11 | |
| 2.70.3 | 5 / 11 | |
| 2.70.2 | 5 / 11 | |
| 2.70.1 | 5 / 11 | |
| 2.70.0 | 5 / 11 | |
| 2.69.7 | 5 / 11 | |
| 2.69.6 | 5 / 11 | |
| 2.69.5 | 5 / 11 | |
| 2.69.4 | 5 / 11 | |
| 2.69.3 | 5 / 11 | |
| 2.69.2 | 5 / 11 | |
| 2.69.1 | 5 / 11 | |
| 2.69.0 | 5 / 11 | |
| 2.68.20 | 5 / 11 | |
| 2.68.19 | 5 / 11 |
v3.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.3
1 findingPackage 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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage 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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.70.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.70.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.70.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.70.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.70.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.70.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.70.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.70.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.69.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.69.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.69.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.69.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.69.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.69.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.69.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.69.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.