@framework-m/vite-plugin
Vite plugin for Framework M plugin auto-discovery and bundling
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@originjs/vite-plugin-federation | AI (phantom-deps): Referenced in config files per finding; not a direct import but legitimately used. | ai | |
| phantom-deps | phantom-dep:@framework-m/plugin-sdk | AI (phantom-deps): Same-org sibling package; declared as dependency for re-export, not direct import — stable FP for this package. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.8.2 | 6 / 11 | |
| 0.8.1 | 6 / 11 | |
| 0.8.0 | 6 / 11 | |
| 0.7.0 | 5 / 11 | |
| 0.6.0 | 5 / 11 | |
| 0.3.9 | 5 / 5 | |
| 0.3.6 | 5 / 5 |
v0.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.