@janiscommerce/view-schema-validator
 [](https://coveralls.io/github/ja
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
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): Established janiscommerce org package; dormancy reflects release cadence, not account takeover indicators. | ai | |
| dependencies | unvetted-dep:@janiscommerce/router-fetcher | AI (dependencies): First-party scoped dep from same org; stable for this package. | ai | |
| dependencies | unvetted-dep:@janiscommerce/endpoint-resolver | AI (dependencies): First-party scoped dep from same org; stable for this package. | ai | |
| dependencies | unvetted-dep:lodash.set | AI (dependencies): lodash.set is a well-known, widely-used utility; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:mock-fs | AI (phantom-deps): mock-fs appears in dependencies but is a test utility; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established org package; lack of provenance is common and not a risk signal here. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 3.14.0 | 13 / 7 | |
| 3.13.0 | 13 / 7 | |
| 3.12.0 | 13 / 7 | |
| 3.11.0 | 13 / 7 | |
| 3.9.0 | 13 / 7 | |
| 3.7.0 | 13 / 7 | |
| 3.2.0 | 13 / 7 | |
| 3.1.0 | 13 / 7 | |
| 3.0.0 | 13 / 7 |
v3.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.