@medusajs/medusa-oas-cli MIT 31 versions

@medusajs/medusa-oas-cli

npm Repository Homepage

OAS CLI

31

Versions

MIT

License

No

Install Scripts

Verified

Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

sebrindomoliverjuhlsradevskiolijuhl

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Transition to GitHub Actions publisher is confirmed by SLSA provenance attestation; consistent with medusajs monorepo CI/CD migration.	ai	2026/05/31
phantom-deps	phantom-dep:@types/lodash	AI (phantom-deps): Type-only package loaded by convention; stable false positive for this package.	ai	2026/05/30
phantom-deps	phantom-dep:@medusajs/utils	AI (phantom-deps): Same-org sibling package; phantom-dep heuristic false positive.	ai	2026/05/30
phantom-deps	phantom-dep:yargs	AI (phantom-deps): yargs is a declared dep used as a CLI framework; phantom-dep heuristic false positive for this package.	ai	2026/05/29
phantom-deps	phantom-dep:@readme/json-schema-ref-parser	AI (phantom-deps): Declared dep used indirectly via @readme/openapi-parser; stable false positive for this package.	ai	2026/05/29

Versions (showing 31 of 31)

Version	Deps	Published
2.15.5	11 / 1	2026-05-29
2.15.3	11 / 1	2026-05-21
2.15.2	11 / 1	2026-05-13
2.15.1	11 / 1	2026-05-11
2.15.0	11 / 1	2026-05-11
2.14.2	11 / 1	2026-04-30
2.14.1	11 / 1	2026-04-24
2.13.5	11 / 1	2026-03-25
2.13.4	11 / 1	2026-03-14
2.13.3	11 / 1	2026-02-27
2.13.2	11 / 1	2026-02-26
2.13.1	11 / 1	2026-01-25
2.13.0	11 / 1	2026-01-22
2.12.6	11 / 1	2026-01-22
2.12.5	11 / 1	2026-01-09
2.12.4	11 / 1	2026-01-06
2.12.3	11 / 1	2025-12-17
2.11.3	11 / 1	2025-11-05
2.11.2	12 / 8	2025-10-31
2.11.0	12 / 8	2025-10-21
2.10.3	12 / 8	2025-09-18
2.10.1	12 / 8	2025-08-28
2.8.8	12 / 8	2025-07-24
2.8.7	12 / 8	2025-07-08
2.8.6	12 / 8	2025-06-30
2.8.5	12 / 8	2025-06-25
2.8.4	12 / 8	2025-06-05
2.8.3	12 / 8	2025-05-22
2.8.2	12 / 8	2025-05-16
2.8.1	12 / 8	2025-05-15
2.8.0	12 / 8	2025-05-13

v2.15.5

2 findings

HIGH Publisher changed: olijuhl → GitHub Actions (on 2026-05-29) provenance

This version was published by a different npm account than previous versions on 2026-05-29. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.15.3

2 findings

HIGH Publisher changed: olijuhl → GitHub Actions (on 2026-05-21) provenance

This version was published by a different npm account than previous versions on 2026-05-21. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.15.2

1 finding

LOW No provenance attestation provenance

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

v2.15.1

1 finding

LOW No provenance attestation provenance

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

v2.15.0

1 finding

LOW No provenance attestation provenance

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

v2.14.2

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.

v2.14.1

2 findings

HIGH Publisher changed: owjuhl → olijuhl (on 2026-04-24) provenance

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

v2.13.5

2 findings

HIGH Publisher changed: owjuhl → olijuhl (on 2026-03-25) provenance

This version was published by a different npm account than previous versions on 2026-03-25. 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.

v2.13.4

2 findings

HIGH Publisher changed: owjuhl → olijuhl (on 2026-03-14) provenance

This version was published by a different npm account than previous versions on 2026-03-14. 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.

v2.13.3

2 findings

HIGH Publisher changed: owjuhl → olijuhl (on 2026-02-27) provenance

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

v2.13.2

2 findings

HIGH Publisher changed: owjuhl → olijuhl (on 2026-02-26) provenance

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

v2.13.1

2 findings

HIGH Publisher changed: owjuhl → olijuhl (on 2026-01-25) provenance

This version was published by a different npm account than previous versions on 2026-01-25. 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.

v2.13.0

2 findings

HIGH Publisher changed: owjuhl → olijuhl (on 2026-01-22) provenance

This version was published by a different npm account than previous versions on 2026-01-22. 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.

v2.12.6

2 findings

HIGH Publisher changed: owjuhl → olijuhl (on 2026-01-22) provenance

This version was published by a different npm account than previous versions on 2026-01-22. 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.

v2.12.5

2 findings

HIGH Publisher changed: owjuhl → olijuhl (on 2026-01-09) provenance

This version was published by a different npm account than previous versions on 2026-01-09. 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.

v2.12.4

2 findings

HIGH Publisher changed: owjuhl → olijuhl (on 2026-01-06) provenance

This version was published by a different npm account than previous versions on 2026-01-06. 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.

v2.12.3

2 findings

HIGH Publisher changed: owjuhl → olijuhl (on 2025-12-17) provenance

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

v2.11.3

1 finding

LOW No provenance attestation provenance

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

v2.11.2

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: owjuhl.

LOW No provenance attestation provenance

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

v2.11.0

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: owjuhl.

LOW No provenance attestation provenance

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

v2.10.3

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: owjuhl.

LOW No provenance attestation provenance

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

v2.10.1

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: owjuhl.

LOW No provenance attestation provenance

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

v2.8.8

1 finding

LOW No provenance attestation provenance

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

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

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

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

v2.8.4

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.

v2.8.3

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.

v2.8.2

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.

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

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