← Home

@axinom/mosaic-graphql-codegen-plugins

Library of graphql-codegen plugins for Mosaic workflows

5
Versions
PROPRIETARY
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

schwendneraxinom_kuzminruwanxaxinomnpm

Keywords

axinommosaicaxinom mosaic

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Only ~12% of npm packages have provenance; common for established packages. ai
license uncommon-license:PROPRIETARY AI (license): Proprietary license is appropriate for internal Axinom package; stable across versions. ai
bogus-package bogus-package AI (bogus-package): Scoped internal library; minimal README and no external links are normal for private/internal packages. ai
dependencies unvetted-dep:handlebars AI (dependencies): handlebars is a well-known templating library; its use in a graphql-codegen plugin is expected and benign. ai

Versions (showing 5 of 5)

Version Deps Published
0.7.0 2 / 6
0.6.0 2 / 6
0.5.0 2 / 6
0.4.0 2 / 6
0.2.0 2 / 6

v0.7.0

1 finding
LOW No provenance attestation provenance

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

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. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.0

1 finding
INFO No provenance attestation provenance

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