@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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Versions (showing 22 of 22)
| 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 | |
| 1.0.12 | 0 / 15 | |
| 1.0.11 | 0 / 12 | |
| 1.0.9 | 0 / 11 | |
| 1.0.8 | 0 / 11 | |
| 1.0.7 | 0 / 11 | |
| 1.0.6 | 0 / 11 | |
| 1.0.5 | 0 / 11 | |
| 1.0.4 | 0 / 11 | |
| 1.0.3 | 0 / 11 | |
| 1.0.2 | 0 / 10 | |
| 1.0.1 | 0 / 10 |
v1.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.