@redocly/portal-plugin-async-api

Async API plugin for Redocly products

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

romanhotsiyalawaradamaltmanmarshevskyyvolodymyr-rutskyislavikbezkorovainyi

Keywords

redoclythemeAsyncAPI

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 their multi-package release automation pattern.	ai	2026/05/29
bogus-package	bogus-package	AI (bogus-package): Commercial Redocly plugin; sparse README and no public repo URL is expected for this package family.	ai	2026/05/27
phantom-deps	phantom-dep:buffer	AI (phantom-deps): buffer is a runtime dep used as a polyfill in bundler config; stable false positive for this package.	ai	2026/04/30
phantom-deps	phantom-dep:events	AI (phantom-deps): events is a runtime dep used as a polyfill in bundler config; stable false positive for this package.	ai	2026/04/30

Versions (showing 40 of 40)

Version	Deps	Published
1.16.1	6 / 5	2026-05-29
1.16.0	6 / 5	2026-05-14
1.15.2	6 / 5	2026-05-06
1.15.1	6 / 5	2026-04-28
1.15.0	6 / 5	2026-04-14
1.14.4	6 / 5	2026-04-08
1.14.3	6 / 5	2026-04-07
1.14.2	6 / 5	2026-03-24
1.14.1	6 / 5	2026-03-20
1.14.0	6 / 5	2026-03-12
1.13.4	6 / 5	2026-02-20
1.13.3	6 / 5	2026-02-19
1.13.2	6 / 5	2026-02-13
1.13.1	6 / 5	2026-02-11
1.13.0	6 / 5	2026-02-10
1.12.2	6 / 5	2026-01-16
1.12.1	6 / 5	2026-01-13
1.12.0	6 / 5	2026-01-12
1.11.1	6 / 5	2025-12-22
1.11.0	6 / 5	2025-12-09
1.10.0	6 / 5	2025-11-06
1.9.2	6 / 5	2025-10-16
1.9.1	6 / 5	2025-10-09
1.9.0	6 / 5	2025-10-08
1.8.3	6 / 5	2025-09-22
1.8.2	6 / 5	2025-09-15
1.8.1	6 / 5	2025-09-10
1.8.0	6 / 5	2025-09-04
1.7.3	6 / 5	2025-08-12
1.7.2	6 / 5	2025-08-12
1.7.1	6 / 5	2025-08-12
1.7.0	6 / 5	2025-08-07
1.6.1	6 / 5	2025-07-17
1.6.0	6 / 5	2025-07-03
1.5.3	6 / 5	2025-06-23
1.5.2	6 / 5	2025-06-19
1.5.1	6 / 5	2025-06-11
1.5.0	6 / 5	2025-06-10
1.4.1	6 / 5	2025-05-06
1.4.0	6 / 5	2025-05-05

v1.16.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.16.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.15.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.15.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.15.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.14.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.14.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.14.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.14.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.14.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.13.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.13.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.13.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.13.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.13.0

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: romanhotsiy → volodymyr-rutskyi (on 2026-02-10, known maintainer) provenance

This version was published by a different npm account (volodymyr-rutskyi) than the most recent previously approved version (romanhotsiy) on 2026-02-10, but volodymyr-rutskyi is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.12.2

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: volodymyr-rutskyi → romanhotsiy (on 2026-01-16, known maintainer) provenance

This version was published by a different npm account (romanhotsiy) than the most recent previously approved version (volodymyr-rutskyi) on 2026-01-16, but romanhotsiy is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.12.1

2 findings

HIGH Publisher changed: volodymyr-rutskyi → GitHub Actions (on 2026-01-13) provenance

This 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.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.12.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.11.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.11.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.10.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.9.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.9.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.9.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.8.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.8.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.8.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.8.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.6.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.6.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.5.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.5.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.5.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.5.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.