@module-federation/vite
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:vitest | AI (typosquat): Scoped package @module-federation/vite is a legitimate Vite plugin, not a typosquat of vitest. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require resolves package.json for a named dependency version lookup; benign pattern stable across versions. | ai |
Versions (showing 74 of 74)
| Version | Deps | Published |
|---|---|---|
| 1.19.1 | 3 / 10 | |
| 1.19.0 | 3 / 10 | |
| 1.18.2 | 3 / 10 | |
| 1.18.1 | 3 / 10 | |
| 1.18.0 | 3 / 10 | |
| 1.17.1 | 3 / 10 | |
| 1.17.0 | 3 / 10 | |
| 1.16.16 | 3 / 10 | |
| 1.16.15 | 3 / 10 | |
| 1.16.14 | 3 / 10 | |
| 1.16.13 | 3 / 10 | |
| 1.16.12 | 3 / 10 | |
| 1.16.11 | 3 / 10 | |
| 1.16.10 | 3 / 10 | |
| 1.16.9 | 3 / 10 | |
| 1.16.8 | 3 / 10 | |
| 1.16.7 | 3 / 10 | |
| 1.16.6 | 3 / 10 | |
| 1.16.5 | 6 / 9 | |
| 1.16.4 | 6 / 10 | |
| 1.16.3 | 6 / 10 | |
| 1.16.2 | 6 / 10 | |
| 1.16.1 | 6 / 10 | |
| 1.16.0 | 6 / 10 | |
| 1.15.5 | 6 / 10 | |
| 1.15.4 | 6 / 10 | |
| 1.15.3 | 6 / 10 | |
| 1.15.2 | 6 / 9 | |
| 1.15.1 | 9 / 9 | |
| 1.15.0 | 9 / 9 | |
| 1.14.5 | 9 / 9 | |
| 1.14.4 | 9 / 11 | |
| 1.14.3 | 9 / 11 | |
| 1.14.2 | 9 / 11 | |
| 1.14.1 | 9 / 11 | |
| 1.14.0 | 9 / 11 | |
| 1.13.7 | 9 / 11 | |
| 1.13.6 | 9 / 11 | |
| 1.11.1 | 8 / 11 | |
| 1.11.0 | 8 / 12 | |
| 1.10.0 | 8 / 12 | |
| 1.9.8 | 8 / 12 | |
| 1.9.7 | 8 / 12 | |
| 1.9.6 | 8 / 12 | |
| 1.9.5 | 8 / 12 | |
| 1.9.4 | 7 / 12 | |
| 1.9.3 | 7 / 12 | |
| 1.9.2 | 7 / 12 | |
| 1.9.1 | 7 / 12 | |
| 1.9.0 | 7 / 12 | |
| 1.7.2 | 6 / 12 | |
| 1.5.0 | 6 / 11 | |
| 1.4.1 | 6 / 11 | |
| 1.4.0 | 6 / 11 | |
| 1.3.0 | 6 / 11 | |
| 1.2.7 | 6 / 11 | |
| 1.2.6 | 6 / 11 | |
| 1.2.5 | 6 / 11 | |
| 1.2.4 | 6 / 11 | |
| 1.2.3 | 6 / 11 | |
| 1.2.2 | 6 / 11 | |
| 1.2.1 | 6 / 11 | |
| 1.2.0 | 6 / 11 | |
| 1.1.9 | 6 / 11 | |
| 1.1.8 | 6 / 11 | |
| 1.1.7 | 7 / 10 | |
| 1.1.6 | 7 / 10 | |
| 1.1.5 | 7 / 10 | |
| 1.1.4 | 7 / 10 | |
| 1.1.3 | 7 / 10 | |
| 1.1.2 | 7 / 10 | |
| 1.1.1 | 7 / 7 | |
| 1.1.0 | 7 / 7 | |
| 1.0.0 | 6 / 6 |
v1.19.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.19.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.18.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.18.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.18.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.17.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.17.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.16.16
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.16.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.16.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.16.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.16.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
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.