oas No license 42 versions

oas

npm Repository Homepage

42

Versions

—

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

gkobergerdomharringtonmjcuvajonursenbachrafegoldbergdannobytesdarrenyong

Keywords

apiapisopenapiopenapi initiativeopenapi specificationopenapi specopenapi documentoaioasapidocmicroservicedocumentation

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
npm-metadata	url-dep:jest-expect-openapi	AI (npm-metadata): Monorepo file: reference in devDependencies only; no runtime impact.	ai	2026/05/17
npm-metadata	url-dep:@readme/oas-examples	AI (npm-metadata): Monorepo file: reference in devDependencies only; no runtime impact.	ai	2026/05/17
npm-metadata	url-dep:jest-expect-jsonschema	AI (npm-metadata): Monorepo file: reference in devDependencies only; no runtime impact.	ai	2026/05/17
typosquat	typosquat.levenshtein:koa	AI (typosquat): 'oas' is a well-known acronym for OpenAPI Specification; this 3325-day-old package with 332 versions is not a typosquat of 'koa'.	ai	2026/04/25
phantom-deps	phantom-dep:@types/json-schema	AI (phantom-deps): @types/json-schema is intentionally a runtime dep for re-exported TypeScript types in this OpenAPI tooling library; stable pattern for this package.	ai	2026/04/25
typosquat	typosquat.levenshtein:cors	AI (typosquat): 'oas' stands for OpenAPI Specification; not a typosquat of 'cors'. Package has 332 versions and 3325 days of history.	ai	2026/04/25
typosquat	typosquat.levenshtein:qs	AI (typosquat): 'oas' stands for OpenAPI Specification; not a typosquat of 'qs'. Package has 332 versions and 3325 days of history.	ai	2026/04/25

Versions (showing 42 of 42)

Version	Deps	Published
33.2.0	10 / 9	2026-05-27
33.1.5	10 / 9	2026-05-18
33.1.4	10 / 9	2026-05-11
33.1.3	10 / 9	2026-05-08
33.0.0	10 / 9	2026-05-01
32.1.18	10 / 9	2026-04-27
32.1.17	10 / 9	2026-04-23
32.1.16	10 / 9	2026-04-22
32.1.15	10 / 9	2026-04-20
32.1.14	10 / 9	2026-04-15
32.1.13	10 / 9	2026-04-15
32.1.11	10 / 9	2026-04-10
32.1.10	10 / 9	2026-04-07
32.1.9	10 / 9	2026-04-07
32.1.8	10 / 9	2026-04-07
32.1.7	10 / 9	2026-04-06
32.1.6	10 / 9	2026-04-02
32.1.5	10 / 9	2026-04-02
32.1.4	10 / 9	2026-03-31
32.1.3	10 / 9	2026-03-31
32.1.2	10 / 9	2026-03-30
32.1.1	10 / 9	2026-03-27
32.1.0	10 / 9	2026-03-23
32.0.0	10 / 9	2026-03-20
31.1.2	10 / 8	2026-03-03
31.1.1	10 / 8	2026-03-03
31.0.0	10 / 8	2026-03-02
29.0.1	9 / 7	2026-02-05
29.0.0	9 / 7	2026-02-05
28.9.0	9 / 7	2026-01-16
28.8.3	9 / 7	2026-01-10
28.8.2	9 / 7	2026-01-08
28.8.1	9 / 7	2026-01-08
28.8.0	9 / 7	2026-01-06
28.7.0	9 / 7	2025-12-18
28.6.3	9 / 7	2025-12-16
28.6.2	9 / 7	2025-12-16
28.6.1	9 / 7	2025-12-12
28.6.0	9 / 7	2025-12-12
28.5.1	9 / 7	2025-11-11
28.5.0	9 / 7	2025-10-29
28.4.0	9 / 7	2025-10-28

v33.2.0

1 finding

LOW No provenance attestation provenance

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

v33.1.5

1 finding

LOW No provenance attestation provenance

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

v33.1.4

1 finding

LOW No provenance attestation provenance

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

v33.1.3

1 finding

LOW No provenance attestation provenance

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

v33.0.0

1 finding

LOW No provenance attestation provenance

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

v32.1.18

1 finding

LOW No provenance attestation provenance

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

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

v32.1.16

1 finding

LOW No provenance attestation provenance

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

v32.1.15

1 finding

LOW No provenance attestation provenance

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

v32.1.14

1 finding

LOW No provenance attestation provenance

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

v32.1.13

1 finding

LOW No provenance attestation provenance

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

v32.1.11

1 finding

LOW No provenance attestation provenance

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

v32.1.10

1 finding

LOW No provenance attestation provenance

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

v32.1.9

1 finding

LOW No provenance attestation provenance

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

v32.1.8

1 finding

LOW No provenance attestation provenance

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

v32.1.7

1 finding

LOW No provenance attestation provenance

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

v32.1.6

1 finding

LOW No provenance attestation provenance

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

v32.1.5

1 finding

LOW No provenance attestation provenance

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

v32.1.4

1 finding

LOW No provenance attestation provenance

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

v32.1.3

1 finding

LOW No provenance attestation provenance

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

v32.1.2

1 finding

LOW No provenance attestation provenance

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

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

v32.1.0

1 finding

LOW No provenance attestation provenance

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

v32.0.0

1 finding

LOW No provenance attestation provenance

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

v31.1.2

1 finding

LOW No provenance attestation provenance

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

v31.1.1

1 finding

LOW No provenance attestation provenance

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

v31.0.0

1 finding

LOW No provenance attestation provenance

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

v29.0.1

1 finding

LOW No provenance attestation provenance

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

v29.0.0

1 finding

LOW No provenance attestation provenance

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

v28.9.0

1 finding

LOW No provenance attestation provenance

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

v28.8.3

1 finding

LOW No provenance attestation provenance

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

v28.8.2

1 finding

LOW No provenance attestation provenance

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

v28.8.1

1 finding

LOW No provenance attestation provenance

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

v28.8.0

1 finding

LOW No provenance attestation provenance

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

v28.7.0

1 finding

LOW No provenance attestation provenance

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

v28.6.3

1 finding

LOW No provenance attestation provenance

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

v28.6.2

1 finding

LOW No provenance attestation provenance

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

v28.6.1

1 finding

LOW No provenance attestation provenance

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

v28.6.0

1 finding

LOW No provenance attestation provenance

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

v28.5.1

1 finding

LOW No provenance attestation provenance

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

v28.5.0

1 finding

LOW No provenance attestation provenance

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

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