← Home

@redocly/portal-legacy-ui

npm
19
Versions
—
License
No
Install Scripts
Missing
Provenance

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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

romanhotsiyalawaradamaltmanmarshevskyyvolodymyr-rutskyislavikbezkorovainyi

Keywords

themeredocly

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Internal Redocly org maintainer reshuffle; no code/dep/script diff accompanies it. ai
maintainer-change maintainer-added AI (maintainer-change): Scoped org package; personnel change without behavioral diff. ai
maintainer-change maintainer-removed AI (maintainer-change): Consistent with the same org-internal transition. ai

Versions (showing 19 of 19)

Version Deps Published
0.18.0 0 / 11
0.17.0 0 / 11
0.16.0 0 / 11
0.15.0 0 / 11
0.14.0 0 / 11
0.13.0 0 / 11
0.12.0 0 / 11
0.11.0 0 / 11
0.10.0 0 / 11
0.9.0 0 / 11
0.8.0 0 / 11
0.7.0 0 / 12
0.6.0 0 / 12
0.5.0 0 / 12
0.4.0 0 / 12
0.3.0 0 / 12
0.2.0 0 / 12
0.1.1 0 / 12
0.1.0 0 / 12

v0.18.0

1 finding
LOW No provenance attestation provenance

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

v0.3.0

2 findings
HIGH Publisher changed: marshevskyy → volodymyr-rutskyi (on 2025-04-02) provenance

This version was published by a different npm account than previous versions on 2025-04-02. 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.

v0.2.0

2 findings
HIGH Publisher changed: marshevskyy → volodymyr-rutskyi (on 2025-03-05) provenance

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.

LOW No provenance attestation provenance

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

v0.1.1

1 finding
LOW No provenance attestation provenance

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

v0.1.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.