@module-federation/automatic-vendor-federation
Utility to enable automatic vendor sharing within bundles using Module Federation
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Publish env change without evidence of compromise; trusted publisher track record. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Intentional pattern: resolves package.json paths to read version strings; stable across versions of this package. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 1.2.1 | 1 / 9 | |
| 1.2.0 | 1 / 9 | |
| 1.1.0 | 1 / 9 | |
| 1.0.1 | 0 / 9 | |
| 1.0.0 | 0 / 9 |
v1.2.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: zackljackson.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: zackljackson.
Package 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.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.