@module-federation/esbuild
This package provides an esbuild plugin for Module Federation, enabling you to easily share code between independently built and deployed applications.
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher has strong track record; likely legitimate org maintainer rotation. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Expected alongside maintainer transition, no other malicious signal. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Consistent with publisher change; trusted account. | ai | |
| phantom-deps | phantom-dep:@rollup/plugin-node-resolve | AI (phantom-deps): Framework plugin loaded by convention, not direct import. | ai | |
| phantom-deps | phantom-dep:rollup-plugin-node-externals | AI (phantom-deps): Build tool plugin; loaded by convention in config. | ai | |
| phantom-deps | phantom-dep:@rollup/plugin-commonjs | AI (phantom-deps): Framework plugin loaded by convention, not direct import. | ai | |
| phantom-deps | phantom-dep:rollup | AI (phantom-deps): Build tool; rollup loaded by convention in config, not direct import. | ai | |
| phantom-deps | phantom-dep:@rollup/plugin-replace | AI (phantom-deps): Framework plugin loaded by convention, not direct import. | ai | |
| phantom-deps | phantom-dep:@module-federation/sdk | AI (phantom-deps): Same org scope; declared as runtime dep, indirect import pattern is stable for this package. | ai | |
| phantom-deps | phantom-dep:@hyrious/esbuild-plugin-commonjs | AI (phantom-deps): Referenced in config files as documented; not a direct import by design. | ai | |
| phantom-deps | phantom-dep:@chialab/esbuild-plugin-commonjs | AI (phantom-deps): Referenced in config files as documented; not a direct import by design. | ai |
Versions (showing 100 of 109)
| Version | Deps | Published |
|---|---|---|
| 0.0.111 | 11 / 2 | |
| 0.0.110 | 11 / 2 | |
| 0.0.109 | 11 / 1 | |
| 0.0.108 | 11 / 1 | |
| 0.0.107 | 11 / 1 | |
| 0.0.106 | 11 / 1 | |
| 0.0.105 | 11 / 1 | |
| 0.0.104 | 11 / 1 | |
| 0.0.103 | 11 / 1 | |
| 0.0.102 | 11 / 1 | |
| 0.0.101 | 11 / 1 | |
| 0.0.100 | 11 / 1 | |
| 0.0.99 | 11 / 1 | |
| 0.0.98 | 9 / 1 | |
| 0.0.97 | 9 / 1 | |
| 0.0.96 | 9 / 1 | |
| 0.0.95 | 9 / 1 | |
| 0.0.94 | 9 / 1 | |
| 0.0.93 | 9 / 1 | |
| 0.0.92 | 9 / 1 | |
| 0.0.91 | 9 / 1 | |
| 0.0.90 | 9 / 1 | |
| 0.0.89 | 9 / 1 | |
| 0.0.88 | 9 / 1 | |
| 0.0.87 | 9 / 1 | |
| 0.0.86 | 9 / 1 | |
| 0.0.85 | 9 / 1 | |
| 0.0.84 | 9 / 1 | |
| 0.0.83 | 9 / 1 | |
| 0.0.82 | 9 / 1 | |
| 0.0.81 | 14 / 0 | |
| 0.0.80 | 14 / 0 | |
| 0.0.79 | 14 / 0 | |
| 0.0.78 | 14 / 0 | |
| 0.0.77 | 14 / 0 | |
| 0.0.76 | 14 / 0 | |
| 0.0.75 | 14 / 0 | |
| 0.0.74 | 14 / 0 | |
| 0.0.73 | 14 / 0 | |
| 0.0.72 | 14 / 0 | |
| 0.0.71 | 14 / 0 | |
| 0.0.70 | 14 / 0 | |
| 0.0.69 | 14 / 0 | |
| 0.0.68 | 14 / 0 | |
| 0.0.67 | 14 / 0 | |
| 0.0.66 | 14 / 0 | |
| 0.0.65 | 14 / 0 | |
| 0.0.64 | 14 / 0 | |
| 0.0.63 | 14 / 0 | |
| 0.0.62 | 14 / 0 | |
| 0.0.61 | 14 / 0 | |
| 0.0.60 | 14 / 0 | |
| 0.0.59 | 14 / 0 | |
| 0.0.58 | 14 / 0 | |
| 0.0.57 | 14 / 0 | |
| 0.0.56 | 14 / 0 | |
| 0.0.55 | 14 / 0 | |
| 0.0.54 | 14 / 0 | |
| 0.0.53 | 14 / 0 | |
| 0.0.52 | 14 / 0 | |
| 0.0.51 | 14 / 0 | |
| 0.0.50 | 14 / 0 | |
| 0.0.49 | 14 / 0 | |
| 0.0.48 | 14 / 0 | |
| 0.0.47 | 14 / 0 | |
| 0.0.46 | 14 / 0 | |
| 0.0.45 | 14 / 0 | |
| 0.0.44 | 14 / 0 | |
| 0.0.43 | 14 / 0 | |
| 0.0.42 | 14 / 0 | |
| 0.0.41 | 14 / 0 | |
| 0.0.40 | 14 / 0 | |
| 0.0.38 | 14 / 0 | |
| 0.0.37 | 14 / 0 | |
| 0.0.36 | 14 / 0 | |
| 0.0.35 | 14 / 0 | |
| 0.0.34 | 14 / 0 | |
| 0.0.33 | 14 / 0 | |
| 0.0.32 | 14 / 0 | |
| 0.0.31 | 14 / 0 | |
| 0.0.30 | 14 / 0 | |
| 0.0.29 | 14 / 0 | |
| 0.0.28 | 14 / 0 | |
| 0.0.27 | 14 / 0 | |
| 0.0.26 | 14 / 0 | |
| 0.0.25 | 14 / 0 | |
| 0.0.24 | 14 / 0 | |
| 0.0.23 | 14 / 0 | |
| 0.0.22 | 14 / 0 | |
| 0.0.21 | 14 / 0 | |
| 0.0.20 | 14 / 0 | |
| 0.0.19 | 14 / 0 | |
| 0.0.18 | 14 / 0 | |
| 0.0.17 | 14 / 0 | |
| 0.0.16 | 14 / 0 | |
| 0.0.15 | 14 / 0 | |
| 0.0.14 | 14 / 0 | |
| 0.0.13 | 14 / 0 | |
| 0.0.12 | 14 / 0 | |
| 0.0.11 | 14 / 0 |
v0.0.111
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.110
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.65
2 findingsThis version was published by a different npm account than previous versions on 2025-04-22. 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.
v0.0.64
2 findingsThis version was published by a different npm account than previous versions on 2025-04-15. 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.
v0.0.63
2 findingsThis version was published by a different npm account than previous versions on 2025-04-08. 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.
v0.0.62
2 findingsThis version was published by a different npm account than previous versions on 2025-04-01. 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.
v0.0.61
2 findingsThis version was published by a different npm account than previous versions on 2025-03-25. 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.
v0.0.60
2 findingsThis version was published by a different npm account than previous versions on 2025-03-18. 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.
v0.0.59
2 findingsThis version was published by a different npm account than previous versions on 2025-03-17. 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.
v0.0.58
2 findingsThis version was published by a different npm account than previous versions on 2025-03-04. 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.
v0.0.57
2 findingsThis version was published by a different npm account than previous versions on 2025-02-26. 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.
v0.0.56
2 findingsThis version was published by a different npm account than previous versions on 2025-02-21. 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.
v0.0.55
2 findingsThis version was published by a different npm account than previous versions on 2025-02-19. 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.
v0.0.54
2 findingsThis version was published by a different npm account than previous versions on 2025-02-10. 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.
v0.0.53
2 findingsThis version was published by a different npm account than previous versions on 2025-02-07. 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.
v0.0.52
2 findingsThis version was published by a different npm account than previous versions on 2025-01-16. 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.
v0.0.51
2 findingsThis version was published by a different npm account than previous versions on 2025-01-07. 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.
v0.0.50
2 findingsThis version was published by a different npm account than previous versions on 2024-12-31. 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.
v0.0.49
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.
v0.0.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.