@angular-architects/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 — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:src/tools/fstart-as-data-url.js | AI (source-diff): Base64-encoded bundle used as a data URL for Node federation init; not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:src/tools/fstart-as-data-url.d.ts | AI (source-diff): Type declaration for the Base64 data-URL string; same benign pattern as the .js file. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): Standard dynamic import shim pattern (new Function('modulePath', 'return import(modulePath)')); no user-controlled input. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): Build-tool package legitimately uses child_process for i18n build steps; expected for this package. | ai | |
| phantom-deps | phantom-dep:process | AI (phantom-deps): process polyfill declared as dep for bundler compatibility; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:signale | AI (phantom-deps): signale used transitively via config; stable false positive for this package. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 22.0.0 | 7 / 0 | |
| 21.2.4 | 10 / 0 | |
| 21.2.3 | 10 / 0 | |
| 21.2.2 | 10 / 0 | |
| 21.2.1 | 10 / 0 | |
| 21.2.0 | 10 / 0 | |
| 21.1.1 | 10 / 0 | |
| 21.1.0 | 8 / 0 | |
| 21.0.4 | 8 / 0 | |
| 21.0.3 | 8 / 0 | |
| 20.3.1 | 10 / 0 | |
| 20.3.0 | 8 / 0 |
v22.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v21.2.4
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v21.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v21.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v21.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v21.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v21.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v21.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v21.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.