@softarc/native-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 |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): Fires on federation config loader that requires a user-specified config file path — expected pattern for this build tool. | ai | |
| dependencies | unvetted-dep:@softarc/sheriff-core | AI (dependencies): Same @softarc org; sheriff-core is a known architectural linting dependency used across this package family. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Established org package; missing description is a metadata gap, not a risk signal. | ai | |
| provenance | no-provenance | AI (provenance): 62k weekly downloads and 82 versions; lack of provenance is common for this package's age. | ai | |
| phantom-deps | phantom-dep:esbuild | AI (phantom-deps): esbuild is a declared runtime/build dependency; phantom-dep heuristic is a false positive here. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established scoped org package; missing metadata is cosmetic, not indicative of spam/malware. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 4.3.2 | 5 / 15 | |
| 4.3.1 | 5 / 15 | |
| 4.3.0 | 5 / 15 | |
| 4.2.1 | 5 / 15 | |
| 4.2.0 | 5 / 15 | |
| 4.1.3 | 5 / 0 | |
| 4.1.2 | 5 / 0 | |
| 4.1.1 | 5 / 0 | |
| 4.1.0 | 5 / 0 | |
| 4.0.1 | 5 / 0 | |
| 4.0.0 | 5 / 0 | |
| 3.5.5 | 5 / 0 | |
| 3.5.4 | 5 / 0 | |
| 3.5.3 | 5 / 0 | |
| 3.5.2 | 5 / 0 | |
| 3.5.1 | 5 / 0 | |
| 3.5.0 | 5 / 0 | |
| 3.4.2 | 5 / 0 | |
| 3.4.1 | 5 / 0 | |
| 3.4.0 | 5 / 0 |
v4.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.