← Home

@hitsoft/agco

npm

This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 12.0.4.

3
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

erkan.ugurismail.yilmazbrcelaguven.uysalayseelgorennerenornekgurkan.sanli

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:esm2020/lib/elektra-invoice-logs/elektra-invoice-log/components/elektra-invoice-log.component.mjs AI (source-diff): Angular Ivy compiled output; long lines are inline template/metadata, not obfuscation. ai
source-diff obfuscated-file:esm2020/lib/elektra-invoice-logs/elektra-invoice-log/elektra-invoice-log.module.mjs AI (source-diff): Angular Ivy compiled output; long lines are inline template/metadata, not obfuscation. ai
source-diff obfuscated-file:esm2020/lib/proxy/elektra-invoice-logs/elektra-invoice-log.service.mjs AI (source-diff): Angular Ivy compiled output; long lines are inline template/metadata, not obfuscation. ai
source-diff obfuscated-file:esm2020/lib/components/hit-elektra-invoice-logs/components/hit-elektra-invoice-log.component.mjs AI (source-diff): Angular Ivy compiled output; long lines are inline template/metadata, not obfuscation. ai

Versions (showing 3 of 3)

Version Deps Published
1.0.10 1 / 0
1.0.9 1 / 0
1.0.8 1 / 0

v1.0.10

1 finding
LOW No provenance attestation provenance

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

v1.0.9

6 findings
HIGH New obfuscated file: esm2020/lib/elektra-invoice-logs/elektra-invoice-log/components/elektra-invoice-log.component.mjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: esm2020/lib/elektra-invoice-logs/elektra-invoice-log/elektra-invoice-log.module.mjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: esm2020/lib/proxy/elektra-invoice-logs/elektra-invoice-log.service.mjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: esm2020/lib/components/hit-elektra-invoice-logs/components/hit-elektra-invoice-log.component.mjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

INFO Publisher changed: caglarc → ayseelgorenn (on 2026-06-01, known maintainer) provenance

This version was published by a different npm account (ayseelgorenn) than the most recent previously approved version (caglarc) on 2026-06-01, but ayseelgorenn is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

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