← Home

@zappar/mattercraft-rspack-plugin

npm Homepage

Rspack plugin for building Mattercraft projects

6
Versions
Proprietary
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

cgauldsimon_zapparjordan-zappargeorge.martinsqueralfrancesca.mayjustin_zapparnyan-left

Keywords

mattercraftzapparrspack3darwebxr

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Zappar org migrated to GitLab CI/CD publishing; consistent with legitimate CI/CD transition for this scoped package. ai
npm-metadata suspicious-initial-version AI (npm-metadata): 0.0.0 is a standard initial version for Zappar monorepo packages; consistent across their ecosystem. ai
provenance no-provenance AI (provenance): GitLab CI/CD publisher; provenance attestation not yet configured but no other risk signals present. ai

Versions (showing 6 of 6)

Version Deps Published
0.5.0 1 / 1
0.3.0 1 / 1
0.2.1 1 / 1
0.2.0 1 / 1
0.1.0 1 / 1
0.0.0 1 / 1

v0.5.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.0

3 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitLab CI/CD.

HIGH Publisher changed: nyan-left → GitLab CI/CD (on 2026-04-07) provenance

This version was published by a different npm account than previous versions on 2026-04-07. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.0

3 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitLab CI/CD.

HIGH Publisher changed: nyan-left → GitLab CI/CD (on 2026-04-07) provenance

This version was published by a different npm account than previous versions on 2026-04-07. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.