@module-federation/node
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:node-fetch | AI (phantom-deps): Common dep likely used in bundled dist code not scanned for imports. | ai | |
| phantom-deps | phantom-dep:@module-federation/utilities | AI (phantom-deps): Same-org sibling package, expected phantom in monorepo. | ai | |
| phantom-deps | phantom-dep:@module-federation/enhanced | AI (phantom-deps): Same-org sibling package, expected phantom in monorepo. | ai | |
| phantom-deps | phantom-dep:@module-federation/runtime | AI (phantom-deps): Same-org sibling package, expected phantom in monorepo. | ai | |
| phantom-deps | phantom-dep:@module-federation/sdk | AI (phantom-deps): Same-org sibling package, expected phantom in monorepo. | ai | |
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI publishing with SLSA provenance; consistent with monorepo CI/CD automation for this org. | ai | |
| source-diff | net-exec-file:dist/src/filesystem/stratagies.mjs | AI (source-diff): Legitimate chunk-loading strategies (vm.runInThisContext for local files, fetch for remote chunks) — core MF Node functionality. | ai | |
| source-diff | net-exec-file:dist/src/utils/hot-reload.mjs | AI (source-diff): HMR utility using eval('require') as webpack compat fallback; expected pattern for this package. | ai | |
| source-diff | net-exec-file:dist/src/utils/flush-chunks.mjs | AI (source-diff): Core MF federation state introspection; new Function used to access globalThis, not arbitrary remote code execution. | ai | |
| typosquat | typosquat.levenshtein:zod | AI (typosquat): Scoped package @module-federation/node is not a typosquat of zod; Levenshtein match is a false positive. | ai | |
| phantom-deps | phantom-dep:encoding | AI (phantom-deps): encoding is a declared runtime dep used transitively by node-fetch; stable false positive for this package. | ai |
Versions (showing 50 of 150)
| Version | Deps | Published |
|---|---|---|
| 2.5.2 | 6 / 0 | |
| 2.5.1 | 6 / 0 | |
| 2.5.0 | 6 / 0 | |
| 2.4.2 | 6 / 0 | |
| 2.4.1 | 6 / 0 | |
| 2.4.0 | 6 / 0 | |
| 2.3.2 | 6 / 0 | |
| 2.3.1 | 6 / 0 | |
| 2.3.0 | 6 / 0 | |
| 2.2.15 | 6 / 0 | |
| 2.2.14 | 6 / 0 | |
| 2.2.13 | 6 / 0 | |
| 2.2.12 | 6 / 0 | |
| 2.2.11 | 6 / 0 | |
| 2.2.10 | 6 / 0 | |
| 2.2.9 | 6 / 0 | |
| 2.2.8 | 6 / 0 | |
| 2.2.7 | 6 / 0 | |
| 2.2.6 | 6 / 0 | |
| 2.2.5 | 6 / 0 | |
| 2.2.4 | 6 / 0 | |
| 2.2.3 | 6 / 0 | |
| 2.2.2 | 6 / 0 | |
| 2.2.1 | 6 / 0 | |
| 2.2.0 | 6 / 0 | |
| 2.1.8 | 6 / 0 | |
| 2.1.7 | 6 / 0 | |
| 2.1.6 | 6 / 0 | |
| 2.1.5 | 6 / 0 | |
| 2.1.4 | 6 / 0 | |
| 2.1.3 | 6 / 0 | |
| 2.1.2 | 6 / 0 | |
| 2.1.1 | 6 / 0 | |
| 2.1.0 | 6 / 0 | |
| 2.0.15 | 6 / 0 | |
| 2.0.14 | 6 / 0 | |
| 2.0.13 | 6 / 0 | |
| 2.0.12 | 6 / 0 | |
| 2.0.11 | 5 / 0 | |
| 2.0.10 | 5 / 0 | |
| 2.0.9 | 5 / 0 | |
| 2.0.8 | 5 / 0 | |
| 2.0.7 | 4 / 0 | |
| 2.0.6 | 4 / 0 | |
| 2.0.5 | 4 / 0 | |
| 2.0.4 | 4 / 0 | |
| 2.0.3 | 4 / 0 | |
| 2.0.2 | 4 / 0 | |
| 2.0.1 | 2 / 0 | |
| 2.0.0 | 2 / 0 |
v2.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.