@module-federation/nextjs-mf
Module Federation helper for NextJS
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:eventemitter3 | AI (phantom-deps): Declared in dependencies; used indirectly via build/config. | ai | |
| phantom-deps | phantom-dep:@module-federation/webpack-type | AI (phantom-deps): Declared in dependencies; same-org scoped package used indirectly. | ai | |
| phantom-deps | phantom-dep:webpack-sources | AI (phantom-deps): Declared in dependencies; used indirectly via build/config. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Trusted publisher with extensive approved history; org-level maintainer rotation. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Consistent with org maintainer rotation, not a takeover pattern. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is same-org @module-federation/runtime-core, consistent with existing sibling deps at same version. | ai | |
| phantom-deps | phantom-dep:@module-federation/webpack-bundler-runtime | AI (phantom-deps): Same-org dep declared in package.json; phantom-dep heuristic false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established package with 82k weekly downloads; sparse README/keywords are cosmetic issues only. | ai | |
| install-scripts | install-script:postinstall | AI (install-scripts): Postinstall is a plain echo deprecation notice; no code execution risk. | ai |
Versions (showing 68 of 68)
| Version | Deps | Published |
|---|---|---|
| 8.8.69 | 7 / 4 | |
| 8.8.67 | 6 / 4 | |
| 8.8.66 | 6 / 4 | |
| 8.8.65 | 6 / 4 | |
| 8.8.64 | 6 / 4 | |
| 8.8.63 | 6 / 4 | |
| 8.8.61 | 6 / 4 | |
| 8.8.60 | 6 / 4 | |
| 8.8.57 | 6 / 4 | |
| 8.8.53 | 6 / 3 | |
| 8.8.52 | 6 / 3 | |
| 8.8.51 | 6 / 3 | |
| 8.8.49 | 6 / 3 | |
| 8.8.46 | 6 / 3 | |
| 8.8.44 | 6 / 3 | |
| 8.8.41 | 6 / 3 | |
| 8.8.40 | 6 / 3 | |
| 8.8.37 | 6 / 3 | |
| 8.8.30 | 6 / 1 | |
| 8.8.29 | 6 / 1 | |
| 8.8.9 | 6 / 0 | |
| 8.8.1 | 6 / 0 | |
| 8.7.3 | 6 / 0 | |
| 8.7.2 | 6 / 0 | |
| 8.7.1 | 6 / 0 | |
| 8.7.0 | 6 / 0 | |
| 8.6.4 | 6 / 0 | |
| 8.6.3 | 6 / 0 | |
| 8.6.2 | 7 / 0 | |
| 8.6.1 | 7 / 0 | |
| 8.6.0 | 7 / 0 | |
| 8.5.5 | 7 / 0 | |
| 8.5.4 | 7 / 0 | |
| 8.5.3 | 7 / 0 | |
| 8.5.2 | 7 / 0 | |
| 8.5.1 | 7 / 0 | |
| 8.5.0 | 7 / 0 | |
| 8.4.13 | 6 / 0 | |
| 8.4.12 | 6 / 0 | |
| 8.4.11 | 6 / 0 | |
| 8.4.10 | 6 / 0 | |
| 8.4.9 | 6 / 0 | |
| 8.4.8 | 6 / 0 | |
| 8.4.7 | 6 / 0 | |
| 8.4.6 | 6 / 0 | |
| 8.4.5 | 6 / 0 | |
| 8.4.4 | 6 / 0 | |
| 8.4.3 | 6 / 0 | |
| 8.4.2 | 6 / 0 | |
| 8.4.1 | 6 / 0 | |
| 8.4.0 | 6 / 0 | |
| 8.3.28 | 9 / 0 | |
| 8.3.27 | 9 / 0 | |
| 8.3.26 | 9 / 0 | |
| 8.3.25 | 9 / 0 | |
| 8.3.24 | 9 / 0 | |
| 8.3.23 | 9 / 0 | |
| 8.3.22 | 9 / 0 | |
| 8.3.21 | 9 / 0 | |
| 8.3.20 | 9 / 0 | |
| 8.3.19 | 9 / 0 | |
| 8.3.18 | 9 / 0 | |
| 8.3.17 | 9 / 0 | |
| 8.3.16 | 9 / 0 | |
| 8.3.15 | 9 / 0 | |
| 8.3.14 | 9 / 0 | |
| 8.3.13 | 9 / 0 | |
| 8.3.12 | 9 / 0 |
v8.8.9
2 findingsThis version was published by a different npm account than previous versions on 2024-12-27. 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.
v8.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.