← Home

@redocly/mock-server

npm

Redocly Mock server

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

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

Versions (showing 50 of 50)

Version Deps Published
0.9.0 11 / 14
0.8.1 11 / 14
0.8.0 11 / 14
0.7.0 11 / 17
0.6.1 11 / 17
0.6.0 11 / 17
0.5.17 11 / 17
0.4.0 10 / 16
0.3.16 10 / 16
0.3.15 10 / 16
0.3.14 10 / 16
0.3.13 10 / 16
0.3.12 10 / 16
0.3.11 10 / 16
0.3.10 10 / 16
0.3.9 10 / 16
0.3.8 10 / 16
0.3.7 10 / 16
0.3.6 10 / 16
0.3.5 10 / 16
0.3.4 10 / 16
0.3.3 10 / 16
0.3.2 10 / 16
0.3.1 10 / 16
0.3.0 10 / 16
0.2.19 10 / 16
0.2.18 10 / 16
0.2.17 10 / 16
0.2.16 10 / 16
0.2.15 10 / 16
0.2.14 10 / 16
0.2.13 10 / 16
0.2.11 10 / 16
0.2.10 10 / 16
0.2.9 10 / 16
0.2.8 10 / 16
0.2.7 10 / 16
0.2.6 10 / 16
0.2.5 10 / 16
0.2.4 10 / 16
0.2.3 10 / 16
0.2.2 10 / 16
0.2.1 10 / 16
0.2.0 10 / 16
0.1.5 10 / 16
0.1.4 10 / 23
0.1.3 10 / 23
0.1.2 10 / 23
0.1.1 10 / 23
0.1.0 10 / 23

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

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

v0.2.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.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. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.5

1 finding
LOW No provenance attestation provenance

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

v0.1.4

1 finding
LOW No provenance attestation provenance

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

v0.1.3

1 finding
LOW No provenance attestation provenance

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

v0.1.2

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