@emilgroup/partner-sdk-node Unlicense 16 versions

@emilgroup/partner-sdk-node

npm

OpenAPI client for @emilgroup/partner-sdk-node

16

Versions

Unlicense

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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

ahmed.zenoadobrodey-emilpavlomaksymovalexandrecastroalexeyoleynikedgar-emilemil_engineeringjonathan.chenwojciech_at_emilmaksym-emilyevheniia-emilemil_aleksandravitaly_emilandrii_meleniukiaroslav.ovcharenkohussein.istanboulithomascover42emil-husseinthmdrkachalkazamiulemil-rickmads-emilolga_timchenko

Keywords

axiostypescriptopenapi-clientopenapi-generator@emilgroup/partner-sdk-node

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	missing-githead	AI (provenance): Consistent with prior versions' publish flow; no behavioral change detected.	ai	2026/07/15
publish-pattern	new-deps-added	AI (publish-pattern): form-data/url are standard, well-known deps for an axios-based generated SDK.	ai	2026/07/15
source-diff	large-new-source-files	AI (source-diff): Consistent with regenerated OpenAPI client code, not injected payload.	ai	2026/07/15

Versions (showing 16 of 16)

Version	Deps	Published
1.24.0	3 / 2	2026-07-20
1.14.0	3 / 2	2025-04-16
1.13.0	3 / 2	2025-02-19
1.12.0	3 / 2	2025-02-12
1.11.0	3 / 2	2025-01-22
1.10.0	3 / 2	2025-01-08
1.9.0	3 / 2	2024-12-18
1.8.0	3 / 2	2024-11-27
1.7.0	3 / 2	2024-11-27
1.6.0	3 / 2	2024-11-20
1.5.0	3 / 2	2024-10-30
1.4.0	1 / 1	2024-10-23
1.3.0	1 / 1	2024-09-25
1.1.0	1 / 1	2024-07-31
1.0.1	1 / 1	2024-06-12
1.0.0	1 / 1	2024-07-26

v1.24.0

3 findings

HIGH Complete maintainer takeover detected maintainer-change

All previous maintainers (cover42devs) were replaced by new maintainers (ahmed.zeno, adobrodey-emil, pavlomaksymov, alexandrecastro, alexeyoleynik, edgar-emil, emil_engineering, jonathan.chen, wojciech_at_emil, maksym-emil, yevheniia-emil, emil_aleksandra, vitaly_emil, andrii_meleniuk, iaroslav.ovcharenko, hussein.istanbouli, thomascover42, emil-hussein, thmd, rkachalka, zamiul, emil-rick, mads-emil, olga_timchenko). This is a strong signal of a potential package hijack and requires careful review.

HIGH Publisher changed: cover42devs → emil-hussein (on 2026-07-20) provenance

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

v1.14.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: cover42devs.

LOW No provenance attestation provenance

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

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

v1.12.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: cover42devs.

LOW No provenance attestation provenance

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

v1.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: cover42devs.

LOW No provenance attestation provenance

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

v1.10.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: cover42devs.

LOW No provenance attestation provenance

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

v1.9.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: cover42devs.

LOW No provenance attestation provenance

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

v1.8.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: cover42devs.

LOW No provenance attestation provenance

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

v1.7.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: cover42devs.

LOW No provenance attestation provenance

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

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

v1.5.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: cover42devs.

LOW No provenance attestation provenance

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

v1.4.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: cover42devs.

LOW No provenance attestation provenance

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

v1.3.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: cover42devs.

LOW No provenance attestation provenance

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

v1.1.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: cover42devs.

LOW No provenance attestation provenance

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

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

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