@redocly/mock-server SEE LICENSE IN LICENSE 29 versions

@redocly/mock-server

npm

Redocly Mock server

29

Versions

SEE LICENSE IN LICENSE

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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

romanhotsiyalawaradamaltmanmarshevskyyvolodymyr-rutskyislavikbezkorovainyi

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:yargs	AI (phantom-deps): Used in CLI via ts-node; stable pattern for this package.	ai	2026/04/30
phantom-deps	phantom-dep:js-yaml	AI (phantom-deps): Config parsing dependency; stable for this package.	ai	2026/04/30
phantom-deps	phantom-dep:ts-node	AI (phantom-deps): Runtime CLI dependency; stable for this package.	ai	2026/04/30
phantom-deps	phantom-dep:punycode	AI (phantom-deps): Transitive dependency; stable for this package.	ai	2026/04/30
phantom-deps	phantom-dep:@redocly/ajv	AI (phantom-deps): Same-org scoped dependency; stable for this package.	ai	2026/04/30
phantom-deps	phantom-dep:fast-xml-parser	AI (phantom-deps): XML parsing dependency; stable for this package.	ai	2026/04/30
phantom-deps	phantom-dep:openapi-sampler	AI (phantom-deps): OpenAPI tooling dependency; stable for this package.	ai	2026/04/30
phantom-deps	phantom-dep:swagger2openapi	AI (phantom-deps): OpenAPI conversion dependency; stable for this package.	ai	2026/04/30
phantom-deps	phantom-dep:@redocly/openapi-core	AI (phantom-deps): Same-org scoped dependency; stable for this package.	ai	2026/04/30

Versions (showing 29 of 29)

Version	Deps	Published
0.7.0	11 / 17	2026-05-14
0.6.1	11 / 17	2026-04-28
0.6.0	11 / 17	2026-04-06
0.5.17	11 / 17	2026-04-01
0.4.0	10 / 16	2025-11-19
0.3.16	10 / 16	2025-11-11
0.3.15	10 / 16	2025-11-03
0.3.14	10 / 16	2025-10-24
0.3.13	10 / 16	2025-10-20
0.3.12	10 / 16	2025-10-15
0.3.11	10 / 16	2025-10-13
0.3.10	10 / 16	2025-10-10
0.3.9	10 / 16	2025-10-07
0.3.8	10 / 16	2025-09-29
0.3.7	10 / 16	2025-09-26
0.3.6	10 / 16	2025-09-22
0.3.5	10 / 16	2025-09-12
0.3.4	10 / 16	2025-08-27
0.3.3	10 / 16	2025-08-20
0.3.2	10 / 16	2025-08-04
0.3.1	10 / 16	2025-07-30
0.3.0	10 / 16	2025-07-24
0.2.19	10 / 16	2025-07-17
0.2.18	10 / 16	2025-07-10
0.2.17	10 / 16	2025-06-26
0.2.16	10 / 16	2025-06-19
0.2.15	10 / 16	2025-06-04
0.2.14	10 / 16	2025-05-29
0.2.13	10 / 16	2025-05-02

v0.7.0

1 finding

LOW No provenance attestation provenance

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

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

v0.6.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.5.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.

v0.4.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.16

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

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

1 finding

LOW No provenance attestation provenance

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

v0.3.13

1 finding

LOW No provenance attestation provenance

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

v0.3.12

1 finding

LOW No provenance attestation provenance

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

v0.3.11

1 finding

LOW No provenance attestation provenance

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

v0.3.10

1 finding

LOW No provenance attestation provenance

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

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. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.6

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

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

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. Only ~12% of npm packages have provenance, so this is common but not ideal.