← Home

@axinom/mosaic-fe-samples-host

npm

The host application, React components and hooks used when developing fe-sample scenarios

22
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

schwendneraxinom_kuzminruwanxaxinomnpm

Keywords

axinommosaicaxinom mosaic

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
bogus-package bogus-package AI (bogus-package): Proprietary commercial library from established vendor; sparse README and no public repo URL are expected for this package type. ai

Versions (showing 22 of 22)

Version Deps Published
0.43.0 1 / 21
0.42.0 2 / 21
0.41.0 2 / 21
0.40.0 2 / 21
0.39.0 2 / 22
0.38.0 2 / 22
0.37.0 2 / 22
0.36.0 2 / 22
0.35.0 2 / 22
0.34.0 2 / 22
0.33.0 2 / 22
0.32.0 2 / 22
0.31.0 2 / 22
0.30.0 2 / 21
0.29.0 2 / 21
0.28.0 2 / 21
0.27.0 2 / 21
0.26.0 2 / 21
0.25.0 2 / 21
0.24.0 2 / 21
0.23.0 2 / 21
0.22.0 2 / 21

v0.43.0

1 finding
LOW No provenance attestation provenance

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

v0.32.0

1 finding
LOW No provenance attestation provenance

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

v0.31.0

1 finding
LOW No provenance attestation provenance

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

v0.30.0

1 finding
LOW No provenance attestation provenance

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

v0.29.0

1 finding
LOW No provenance attestation provenance

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

v0.28.0

1 finding
LOW No provenance attestation provenance

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

v0.27.0

1 finding
LOW No provenance attestation provenance

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

v0.26.0

1 finding
LOW No provenance attestation provenance

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

v0.25.0

1 finding
LOW No provenance attestation provenance

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

v0.24.0

1 finding
LOW No provenance attestation provenance

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

v0.23.0

1 finding
LOW No provenance attestation provenance

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

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