@origine-hq/ngx-apps-deployment
This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 18.0.0.
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:fesm2022/origine-hq-ngx-apps-deployment-deployment.module-BnCLOXU1.mjs | AI (source-diff): Standard Angular FESM2022 bundle with long lines from minification; not obfuscated malware. | ai | |
| source-diff | obfuscated-file:fesm2022/origine-hq-ngx-apps-deployment-deployment.module-IGF3uIRb.mjs | AI (source-diff): Standard Angular FESM2022 bundle output; long lines are minified but readable Angular/RxJS code, not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:fesm2022/origine-hq-ngx-apps-deployment-deployment.module-CpStfquC.mjs | AI (source-diff): Standard Angular FESM2022 minified bundle output; long lines are expected for this build format. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a known Angular/TypeScript implicit runtime dependency; phantom-dep false positive for Angular libraries. | ai | |
| source-diff | obfuscated-file:fesm2022/origine-hq-ngx-apps-deployment-deployment.module-BNM7gJNO.mjs | AI (source-diff): Standard Angular FESM2022 minified bundle output; long lines are from bundler, not obfuscation. | ai | |
| source-diff | obfuscated-file:fesm2022/origine-hq-ngx-apps-deployment-deployment.module-C55l3Yj5.mjs | AI (source-diff): Standard Angular FESM2022 bundle with long lines; readable code, not obfuscated. Stable pattern for this package. | ai | |
| source-diff | obfuscated-file:fesm2022/origine-hq-ngx-apps-deployment-deployment.module-LGziOilE.mjs | AI (source-diff): Standard Angular FESM2022 bundle output; long lines are normal for Angular compiled libraries, not obfuscation. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.4.48 | 1 / 0 | |
| 0.2.49 | 1 / 0 | |
| 0.2.47 | 1 / 0 | |
| 0.2.46 | 1 / 0 | |
| 0.2.45 | 1 / 0 | |
| 0.2.43 | 1 / 0 | |
| 0.2.42 | 1 / 0 | |
| 0.2.41 | 1 / 0 | |
| 0.2.39 | 1 / 0 | |
| 0.2.38 | 1 / 0 | |
| 0.2.37 | 1 / 0 | |
| 0.2.35 | 1 / 0 | |
| 0.2.34 | 1 / 0 |
v0.4.48
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.2.49
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.2.47
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.2.46
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.2.45
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.2.43
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.2.42
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.2.41
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.2.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.