← Home

@axinom/mosaic-testing

npm

This library encapsulates testing-related functionality for Mosaic based services.

24
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
publish-pattern dormant-publish AI (publish-pattern): Publisher has approved track record; version diff shows benign changes consistent with internal tooling update. ai
phantom-deps phantom-dep:graphile-build-pg AI (phantom-deps): graphile-build-pg is a declared runtime dep in package.json; phantom-dep heuristic is a false positive here. ai
bogus-package bogus-package AI (bogus-package): Proprietary internal library; sparse README and no public repo URL are expected for this type of package. ai

Versions (showing 24 of 24)

Version Deps Published
0.7.16 11 / 10
0.7.15 11 / 10
0.7.14 11 / 10
0.7.13 11 / 10
0.7.12 11 / 8
0.7.11 11 / 8
0.7.10 11 / 8
0.7.9 11 / 8
0.7.8 11 / 8
0.7.7 11 / 8
0.7.6 11 / 8
0.7.5 11 / 8
0.7.4 11 / 8
0.7.3 11 / 8
0.7.2 11 / 8
0.7.1 11 / 8
0.7.0 11 / 8
0.6.0 11 / 8
0.5.0 11 / 8
0.4.0 11 / 8
0.3.0 11 / 8
0.2.0 11 / 8
0.1.1 11 / 8
0.1.0 11 / 8

v0.7.16

1 finding
LOW No provenance attestation provenance

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

v0.7.3

1 finding
LOW No provenance attestation provenance

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

v0.7.2

1 finding
LOW No provenance attestation provenance

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

v0.7.1

1 finding
LOW No provenance attestation provenance

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

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.6.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. Consider requesting the maintainer enable provenance via CI/CD.

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

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.