← Home

@emilgroup/accounting-sdk

npm

OpenAPI client for @emilgroup/accounting-sdk

21
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/accounting-sdk

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-takeover AI (maintainer-change): Org-wide maintainer consolidation to emil-* accounts, consistent naming, no behavioral change. ai
provenance publisher-changed AI (provenance): Publisher change aligns with same org rebrand; no provenance regression. ai

Versions (showing 21 of 21)

Version Deps Published
1.34.0 1 / 1
1.20.0 1 / 1
1.19.0 1 / 1
1.18.0 1 / 1
1.17.0 1 / 1
1.16.0 1 / 1
1.15.0 1 / 1
1.14.0 1 / 1
1.13.0 1 / 1
1.12.0 1 / 1
1.11.0 1 / 1
1.10.0 1 / 1
1.9.0 1 / 1
1.8.0 1 / 1
1.7.0 1 / 1
1.6.0 1 / 1
1.5.0 1 / 1
1.4.0 1 / 1
1.3.0 1 / 1
1.2.0 1 / 1
1.1.0 1 / 1

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

1 finding
LOW No provenance attestation provenance

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

v1.19.0

1 finding
LOW No provenance attestation provenance

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

v1.18.0

1 finding
LOW No provenance attestation provenance

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

v1.17.0

1 finding
LOW No provenance attestation provenance

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

v1.16.0

1 finding
LOW No provenance attestation provenance

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

v1.15.0

1 finding
LOW No provenance attestation provenance

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

v1.14.0

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

v1.12.0

1 finding
LOW No provenance attestation provenance

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

v1.11.0

1 finding
LOW No provenance attestation provenance

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

v1.10.0

1 finding
LOW No provenance attestation provenance

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

v1.9.0

1 finding
LOW No provenance attestation provenance

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

v1.8.0

1 finding
LOW No provenance attestation provenance

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

v1.7.0

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

v1.5.0

1 finding
LOW No provenance attestation provenance

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

v1.4.0

1 finding
LOW No provenance attestation provenance

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

v1.3.0

1 finding
LOW No provenance attestation provenance

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

v1.2.0

1 finding
LOW No provenance attestation provenance

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

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