← Home

@zappar/mattercraft-bundler-plugins-core

npm Homepage

Shared Mattercraft bundler plugin logic

8
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

mattercraftzappar3darwebxr

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata suspicious-initial-version AI (npm-metadata): Zappar org internal package with restricted access and workspace deps; 0.0.0 is a deliberate versioning choice, not malware indicator. ai
phantom-deps phantom-dep:sharp AI (phantom-deps): sharp is a declared runtime dependency for image processing; phantom-dep heuristic fires because it may be used indirectly via the transformers package. ai

Versions (showing 8 of 8)

Version Deps Published
0.5.0 2 / 0
0.4.0 2 / 0
0.3.1 2 / 0
0.3.0 2 / 0
0.2.1 2 / 0
0.2.0 2 / 0
0.1.0 2 / 0
0.0.0 2 / 0

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.4.0

1 finding
LOW No provenance attestation provenance

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

v0.3.1

1 finding
LOW No provenance attestation provenance

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

v0.3.0

1 finding
LOW No provenance attestation provenance

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

v0.2.1

1 finding
LOW No provenance attestation provenance

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

v0.2.0

1 finding
LOW No provenance attestation provenance

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

v0.1.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.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.