@redocly/asyncapi-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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): volodymyr-rutskyi is an established Redocly org publisher with 45 approved packages; transition appears legitimate. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped Redocly org package; missing repo/homepage in package.json is a metadata gap, not a spam indicator. | ai | |
| phantom-deps | phantom-dep:web-vitals | AI (phantom-deps): Declared runtime dep; phantom-dep heuristic fires on indirect usage patterns common in bundled packages. | ai | |
| phantom-deps | phantom-dep:openapi-sampler | AI (phantom-deps): Declared runtime dep; phantom-dep heuristic fires on indirect usage patterns common in bundled packages. | ai | |
| phantom-deps | phantom-dep:react-router-dom | AI (phantom-deps): Declared runtime dep; phantom-dep heuristic fires on indirect usage patterns common in bundled packages. | ai | |
| phantom-deps | phantom-dep:@redocly/redoc-opentelemetry | AI (phantom-deps): Same-org dep declared in package.json; phantom-dep heuristic is a false positive for this package. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 1.10.0 | 10 / 16 | |
| 1.9.1 | 10 / 16 | |
| 1.9.0 | 10 / 16 | |
| 1.8.1 | 9 / 16 | |
| 1.8.0 | 9 / 16 | |
| 1.7.2 | 9 / 16 | |
| 1.7.1 | 9 / 16 | |
| 1.7.0 | 9 / 16 | |
| 1.6.1 | 9 / 16 | |
| 1.6.0 | 9 / 16 | |
| 1.5.1 | 9 / 16 | |
| 1.5.0 | 9 / 16 | |
| 1.4.0 | 9 / 17 | |
| 1.3.1 | 9 / 17 | |
| 1.3.0 | 9 / 17 | |
| 1.2.1 | 9 / 17 | |
| 1.2.0 | 9 / 17 | |
| 1.1.3 | 9 / 17 | |
| 1.1.2 | 9 / 17 | |
| 1.1.1 | 9 / 17 | |
| 1.1.0 | 9 / 17 | |
| 1.0.0 | 9 / 17 |
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.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
2 findingsThis version was published by a different npm account than previous versions on 2026-01-13. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.1
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.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
2 findingsThis version was published by a different npm account than previous versions on 2025-09-04. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
2 findingsThis version was published by a different npm account than previous versions on 2025-08-12. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
2 findingsThis version was published by a different npm account than previous versions on 2025-08-12. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
2 findingsThis version was published by a different npm account than previous versions on 2025-08-12. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.