@redocly/portal-plugin-soap-api
SOAP API plugin for Redocly products
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
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): Redocly org migrated publishing to GitHub Actions CI; consistent with org-wide CI automation across their package portfolio. | ai |
Versions (showing 51 of 104)
| Version | Deps | Published |
|---|---|---|
| 0.18.0 | 5 / 5 | |
| 0.17.1 | 5 / 5 | |
| 0.17.0 | 5 / 5 | |
| 0.16.1 | 5 / 6 | |
| 0.16.0 | 5 / 6 | |
| 0.15.2 | 5 / 6 | |
| 0.15.1 | 5 / 6 | |
| 0.15.0 | 5 / 6 | |
| 0.14.4 | 5 / 6 | |
| 0.14.3 | 5 / 6 | |
| 0.14.2 | 5 / 6 | |
| 0.14.1 | 5 / 6 | |
| 0.14.0 | 5 / 6 | |
| 0.13.4 | 5 / 6 | |
| 0.13.3 | 5 / 6 | |
| 0.13.2 | 5 / 6 | |
| 0.13.1 | 5 / 6 | |
| 0.13.0 | 5 / 6 | |
| 0.12.2 | 5 / 6 | |
| 0.12.1 | 5 / 6 | |
| 0.12.0 | 5 / 6 | |
| 0.11.1 | 5 / 6 | |
| 0.11.0 | 5 / 6 | |
| 0.10.0 | 5 / 6 | |
| 0.9.2 | 5 / 6 | |
| 0.9.1 | 5 / 6 | |
| 0.9.0 | 5 / 6 | |
| 0.8.3 | 5 / 6 | |
| 0.8.2 | 5 / 6 | |
| 0.8.1 | 5 / 6 | |
| 0.8.0 | 5 / 6 | |
| 0.7.3 | 5 / 6 | |
| 0.7.2 | 5 / 6 | |
| 0.7.1 | 5 / 6 | |
| 0.7.0 | 5 / 6 | |
| 0.6.1 | 5 / 6 | |
| 0.6.0 | 5 / 6 | |
| 0.5.3 | 5 / 6 | |
| 0.5.2 | 5 / 6 | |
| 0.5.1 | 5 / 6 | |
| 0.5.0 | 5 / 6 | |
| 0.4.1 | 5 / 6 | |
| 0.4.0 | 5 / 6 | |
| 0.3.2 | 5 / 6 | |
| 0.3.1 | 5 / 6 | |
| 0.2.1 | 5 / 6 | |
| 0.2.0 | 5 / 6 | |
| 0.1.57 | 5 / 6 | |
| 0.1.56 | 5 / 6 | |
| 0.1.55 | 5 / 6 | |
| 0.1.54 | 5 / 6 |
v0.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2025-03-20. This could indicate a legitimate maintainer transition or an account compromise.
v0.2.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2025-03-05. This could indicate a legitimate maintainer transition or an account compromise.
v0.1.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.