@epam/microfrontends
Provides a set of helpers and CLI tools to facilitate development of micro-frontend widgets.
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
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 1.2.0 | 0 / 20 | |
| 1.1.4 | 0 / 20 | |
| 1.1.3 | 0 / 20 | |
| 1.1.2 | 0 / 15 | |
| 1.1.1 | 0 / 15 | |
| 1.1.0 | 0 / 15 | |
| 1.0.20 | 0 / 15 | |
| 1.0.19 | 0 / 15 | |
| 1.0.15 | 0 / 15 | |
| 1.0.14 | 0 / 15 | |
| 1.0.13 | 0 / 15 |
v1.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.