@hitsoft/e-donusum
This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 12.0.4.
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:esm2020/lib/components/hit-invoices-sent/hit-invoice-sent.component.mjs | AI (source-diff): Angular Ivy compiled output; long lines are normal for this build format, not obfuscation. | ai | |
| source-diff | obfuscated-file:esm2020/lib/components/hit-invoices-sent/hit-invoice-sent.module.mjs | AI (source-diff): Angular Ivy compiled output; long lines are normal for this build format, not obfuscation. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a standard Angular/TypeScript runtime dep; not directly imported in source is expected. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 1.0.122 | 1 / 0 | |
| 1.0.119 | 1 / 0 | |
| 1.0.118 | 1 / 0 | |
| 1.0.117 | 1 / 0 | |
| 1.0.116 | 1 / 0 |
v1.0.122
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (ayseelgorenn) than the most recent previously approved version (guven.uysal) on 2026-04-13, 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.119
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.118
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.117
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.116
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.