@redocly/graphql-docs
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 |
|---|---|---|---|---|
| semgrep | semgrep:new-function-constructor | AI (semgrep): Minified IS_BROWSER check using new Function('try{return this===window}...') — static string, no user input, benign pattern. | ai | |
| phantom-deps | phantom-dep:marked | AI (phantom-deps): Listed as dependency; likely used transitively or in config — stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:deepmerge | AI (phantom-deps): Listed as dependency; likely used transitively or in config — stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:web-vitals | AI (phantom-deps): Listed as dependency; likely used transitively or in config — stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@redocly/redoc-opentelemetry | AI (phantom-deps): Same org scope; stable false positive for this package. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 1.10.0 | 6 / 36 | |
| 1.9.1 | 6 / 36 | |
| 1.9.0 | 6 / 36 | |
| 1.8.0 | 4 / 36 | |
| 1.7.1 | 4 / 36 | |
| 1.7.0 | 4 / 36 | |
| 1.6.0 | 4 / 36 | |
| 1.5.0 | 4 / 36 | |
| 1.4.0 | 4 / 38 | |
| 1.3.0 | 4 / 38 | |
| 1.2.0 | 3 / 38 | |
| 1.1.0 | 3 / 38 | |
| 1.0.0 | 3 / 38 |
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.