@zappar/mattercraft-cli
Build Mattercraft projects from the command line or programmatically
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 |
|---|---|---|---|---|
| npm-metadata | suspicious-initial-version | AI (npm-metadata): 0.0.0 is a standard initial placeholder version in the @zappar monorepo; not indicative of malicious intent. | ai | |
| phantom-deps | phantom-dep:vite | AI (phantom-deps): Vite is a runtime dep used via config files, not direct imports; stable false positive for a CLI build tool. | ai | |
| phantom-deps | phantom-dep:vite-plugin-wasm | AI (phantom-deps): Plugin dep referenced in config, not directly imported; expected pattern for a Vite plugin. | ai | |
| phantom-deps | phantom-dep:@vitejs/plugin-react | AI (phantom-deps): Vite plugin dep used via config files; stable false positive for this CLI tool. | ai | |
| phantom-deps | phantom-dep:@zappar/mattercraft-vite-plugin | AI (phantom-deps): Same-org plugin dep used via config; expected pattern, not a real phantom dep. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.4.0 | 4 / 0 | |
| 0.3.0 | 3 / 0 | |
| 0.2.1 | 3 / 0 | |
| 0.2.0 | 3 / 0 | |
| 0.1.1 | 3 / 0 | |
| 0.1.0 | 3 / 0 | |
| 0.0.0 | 3 / 0 |
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.