@orval/mock
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:mobx | AI (typosquat): Scoped @orval/* package; no relation to mobx, levenshtein match is coincidental. | ai | |
| typosquat | typosquat.levenshtein:mocha | AI (typosquat): Scoped @orval/* package; no relation to mocha, levenshtein match is coincidental. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package; sparse README and no keywords are typical for this package type. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 8.15.0 | 2 / 5 | |
| 8.14.0 | 2 / 5 | |
| 8.13.0 | 2 / 5 | |
| 8.12.3 | 2 / 5 | |
| 8.9.0 | 2 / 5 | |
| 8.8.1 | 2 / 5 | |
| 8.8.0 | 2 / 5 | |
| 8.7.0 | 2 / 5 | |
| 8.6.0 | 2 / 5 | |
| 8.5.3 | 2 / 5 | |
| 8.5.2 | 2 / 5 | |
| 8.5.1 | 2 / 5 | |
| 8.5.0 | 2 / 5 | |
| 8.4.2 | 2 / 5 | |
| 8.4.1 | 1 / 5 | |
| 8.4.0 | 1 / 5 | |
| 8.3.0 | 1 / 5 | |
| 8.2.0 | 1 / 5 | |
| 8.1.0 | 1 / 5 | |
| 8.0.3 | 1 / 5 | |
| 7.21.0 | 2 / 5 | |
| 7.20.0 | 2 / 5 |
v8.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.12.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: melloware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.