@zappar/mattercraft-transformers
Internal transformation library for Mattercraft build plugins
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 |
|---|---|---|---|---|
| npm-metadata | suspicious-initial-version | AI (npm-metadata): Scoped @zappar org package; 0.0.0 is consistent with initial monorepo release, not throwaway malware. | ai | |
| phantom-deps | phantom-dep:@gltf-transform/functions | AI (phantom-deps): Config-only reference; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@babel/plugin-proposal-decorators | AI (phantom-deps): Babel plugin loaded by convention, not directly imported. | ai | |
| phantom-deps | phantom-dep:draco3dgltf | AI (phantom-deps): Referenced in config files for gltf compression pipeline, not directly imported. | ai | |
| phantom-deps | phantom-dep:meshoptimizer | AI (phantom-deps): Referenced in config files for mesh optimization pipeline, not directly imported. | ai | |
| phantom-deps | phantom-dep:@gltf-transform/core | AI (phantom-deps): Referenced in config files, stable false positive for this gltf-transform-based package. | ai | |
| phantom-deps | phantom-dep:@gltf-transform/extensions | AI (phantom-deps): Referenced in config files, stable false positive for this gltf-transform-based package. | ai | |
| phantom-deps | phantom-dep:@babel/core | AI (phantom-deps): Babel core loaded by convention in build pipeline, not directly imported. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.5.0 | 7 / 1 | |
| 0.2.0 | 5 / 0 | |
| 0.0.2 | 5 / 0 | |
| 0.0.1 | 5 / 0 | |
| 0.0.0 | 5 / 0 |
v0.5.0
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.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
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.