@hitsoft/ozsay
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/proxy/prepare-request-dbs/prepare-request-db.service.mjs | AI (source-diff): Angular AOT compiler output. | ai | |
| source-diff | obfuscated-file:esm2020/lib/hit-proxy/parameters/hit-parameter.service.mjs | AI (source-diff): Angular AOT compiler output with long decorator metadata lines; not obfuscation. | ai | |
| source-diff | obfuscated-file:esm2020/lib/components/parameters/hit-parameters.component.mjs | AI (source-diff): Angular AOT compiler output; long lines from inlined templates. | ai | |
| source-diff | obfuscated-file:esm2020/lib/components/parameters/hit-parameters.module.mjs | AI (source-diff): Angular AOT compiler output; standard NgModule metadata. | ai | |
| source-diff | obfuscated-file:esm2020/lib/components/hit-period-logs/hit-period-logs.component.mjs | AI (source-diff): Angular AOT compiler output with inlined template. | ai | |
| source-diff | obfuscated-file:esm2020/lib/components/hit-period-logs/hit-period-logs.module.mjs | AI (source-diff): Angular AOT compiler output; standard NgModule. | ai | |
| source-diff | obfuscated-file:esm2020/lib/period-logs/period-log/components/period-log.component.mjs | AI (source-diff): Angular AOT compiler output. | ai | |
| source-diff | obfuscated-file:esm2020/lib/period-logs/period-log/period-log.module.mjs | AI (source-diff): Angular AOT compiler output. | ai | |
| source-diff | obfuscated-file:esm2020/lib/proxy/period-logs/period-log.service.mjs | AI (source-diff): Angular AOT compiler output; REST service wrapper. | ai | |
| source-diff | obfuscated-file:esm2020/lib/prepare-request-dbs/prepare-request-db/components/prepare-request-db.component.mjs | AI (source-diff): Angular AOT compiler output. | ai | |
| source-diff | obfuscated-file:esm2020/lib/prepare-request-dbs/prepare-request-db/prepare-request-db.module.mjs | AI (source-diff): Angular AOT compiler output. | ai | |
| source-diff | obfuscated-file:esm2020/lib/hit-proxy/hit-periods/traffic-upload-hub.service.mjs | AI (source-diff): File is readable Angular/SignalR service code; long lines are from standard ESM bundle output, not obfuscation. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.0.33 | 1 / 0 | |
| 0.0.32 | 1 / 0 | |
| 0.0.26 | 1 / 0 | |
| 0.0.12 | 1 / 0 | |
| 0.0.10 | 1 / 0 | |
| 0.0.9 | 1 / 0 | |
| 0.0.8 | 1 / 0 | |
| 0.0.7 | 1 / 0 | |
| 0.0.6 | 1 / 0 | |
| 0.0.5 | 1 / 0 | |
| 0.0.4 | 1 / 0 | |
| 0.0.3 | 1 / 0 | |
| 0.0.2 | 1 / 0 |
v0.0.33
2 findingsNewly 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.
v0.0.26
13 findingsThis version was published by a different npm account than previous versions on 2026-04-08. This could indicate a legitimate maintainer transition or an account compromise.
Newly 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.
Newly 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.
Newly 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.
Newly 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.
Newly 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.
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.
v0.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.