@orval/axios
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 orval monorepo sub-package; dormancy likely reflects release cadence, not takeover. No code changes vs prior version. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package; sparse metadata and link-heavy README are expected for orval packages. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Monorepo sub-package pattern; no description is normal across all @orval/* packages. | ai |
Versions (showing 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 8.15.0 | 1 / 5 | |
| 8.14.0 | 1 / 5 | |
| 8.13.0 | 1 / 5 | |
| 8.9.0 | 1 / 5 | |
| 8.8.1 | 1 / 5 | |
| 8.8.0 | 1 / 5 | |
| 8.7.0 | 1 / 5 | |
| 8.6.1 | 1 / 5 | |
| 8.6.0 | 1 / 5 | |
| 8.5.3 | 1 / 5 | |
| 8.5.2 | 1 / 5 | |
| 8.5.1 | 1 / 5 | |
| 8.5.0 | 1 / 5 | |
| 8.4.2 | 1 / 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 / 4 | |
| 8.0.2 | 1 / 4 | |
| 8.0.1 | 1 / 4 | |
| 8.0.0 | 1 / 4 | |
| 7.21.0 | 1 / 4 | |
| 7.20.0 | 1 / 4 | |
| 7.19.0 | 1 / 4 | |
| 7.18.0 | 1 / 4 | |
| 7.17.2 | 1 / 4 | |
| 7.17.0 | 1 / 4 | |
| 7.16.1 | 1 / 4 | |
| 7.16.0 | 1 / 4 |
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.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.1
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.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.
v8.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.0
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. Consider requesting the maintainer enable provenance via CI/CD.
v7.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.17.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.