@redocly/portal-plugin-mock-server No license 34 versions

@redocly/portal-plugin-mock-server

npm

34

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

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/CD adoption across their package suite.	ai	2026/05/06
phantom-deps	phantom-dep:@redocly/mock-server	AI (phantom-deps): Same-org plugin dependency; declared for consumers, not directly imported in this wrapper package.	ai	2026/04/30
phantom-deps	phantom-dep:@redocly/openapi-docs	AI (phantom-deps): Same-org plugin dependency; declared for consumers, not directly imported in this wrapper package.	ai	2026/04/30

Versions (showing 34 of 134)

Version	Deps	Published
0.3.9	4 / 3	2024-08-21
0.3.8	4 / 3	2024-08-20
0.3.7	4 / 3	2024-08-16
0.3.6	4 / 3	2024-08-15
0.3.5	4 / 3	2024-08-14
0.3.4	4 / 3	2024-08-12
0.3.3	4 / 3	2024-08-05
0.3.2	4 / 3	2024-07-23
0.3.1	4 / 3	2024-07-23
0.3.0	4 / 3	2024-07-18
0.2.23	4 / 3	2024-07-17
0.2.22	4 / 3	2024-07-17
0.2.21	4 / 3	2024-07-17
0.2.20	4 / 3	2024-07-16
0.2.19	4 / 3	2024-07-12
0.2.18	4 / 3	2024-07-11
0.2.17	4 / 3	2024-07-11
0.2.16	4 / 3	2024-07-09
0.2.15	4 / 3	2024-07-03
0.2.14	4 / 3	2024-07-02
0.2.13	4 / 3	2024-06-27
0.2.12	4 / 3	2024-06-25
0.2.11	4 / 3	2024-06-25
0.2.10	4 / 3	2024-06-24
0.2.8	4 / 3	2024-06-19
0.2.7	4 / 3	2024-06-18
0.2.6	4 / 3	2024-06-18
0.2.5	4 / 3	2024-06-17
0.2.4	4 / 3	2024-06-11
0.2.3	4 / 3	2024-06-10
0.2.2	4 / 3	2024-06-10
0.2.1	4 / 3	2024-06-06
0.2.0	4 / 3	2024-06-05
0.1.17	4 / 3	2024-04-29

v0.3.9

1 finding

LOW No provenance attestation provenance

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

v0.3.8

1 finding

LOW No provenance attestation provenance

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

v0.3.7

1 finding

LOW No provenance attestation provenance

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

v0.3.6

1 finding

LOW No provenance attestation provenance

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

v0.3.5

1 finding

LOW No provenance attestation provenance

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

v0.3.4

1 finding

LOW No provenance attestation provenance

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

v0.3.3

1 finding

LOW No provenance attestation provenance

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

v0.3.2

1 finding

LOW No provenance attestation provenance

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

v0.3.1

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

LOW No provenance attestation provenance

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

INFO Publisher changed: romanhotsiy → marshevskyy (on 2024-07-18, known maintainer) provenance

This version was published by a different npm account (marshevskyy) than the most recent previously approved version (romanhotsiy) on 2024-07-18, but marshevskyy 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.

v0.2.23

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: marshevskyy → romanhotsiy (on 2024-07-17, known maintainer) provenance

This version was published by a different npm account (romanhotsiy) than the most recent previously approved version (marshevskyy) on 2024-07-17, 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.

v0.2.22

1 finding

LOW No provenance attestation provenance

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

v0.2.21

1 finding

LOW No provenance attestation provenance

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

v0.2.20

1 finding

LOW No provenance attestation provenance

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

v0.2.19

1 finding

LOW No provenance attestation provenance

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

v0.2.18

1 finding

LOW No provenance attestation provenance

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

v0.2.17

1 finding

LOW No provenance attestation provenance

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

v0.2.16

1 finding

LOW No provenance attestation provenance

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

v0.2.15

1 finding

LOW No provenance attestation provenance

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

v0.2.14

1 finding

LOW No provenance attestation provenance

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

v0.2.13

1 finding

LOW No provenance attestation provenance

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

v0.2.12

1 finding

LOW No provenance attestation provenance

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

v0.2.11

1 finding

LOW No provenance attestation provenance

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

v0.2.10

1 finding

LOW No provenance attestation provenance

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

v0.2.8

1 finding

LOW No provenance attestation provenance

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

v0.2.7

1 finding

LOW No provenance attestation provenance

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

v0.2.6

1 finding

LOW No provenance attestation provenance

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

v0.2.5

1 finding

LOW No provenance attestation provenance

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

v0.2.4

1 finding

LOW No provenance attestation provenance

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

v0.2.3

1 finding

LOW No provenance attestation provenance

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

v0.2.2

1 finding

LOW No provenance attestation provenance

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

v0.2.1

1 finding

LOW No provenance attestation provenance

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

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

v0.1.17

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.