@axinom/mosaic-testing
This library encapsulates testing-related functionality for Mosaic based services.
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| 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 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 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 |
v0.7.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.