@authing/ng-ui-components
This project was generated with [Angular CLI](https://github.com/angular/angular-cli) version 14.2.11.
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:esm2015/lib/Guard/guard.component.js | AI (source-diff): Angular build output (fesm2015/esm2015 bundle), not true obfuscation; sample shows clean source. | ai | |
| source-diff | obfuscated-file:fesm2015/authing-ng-ui-components.js | AI (source-diff): Angular fesm2015 bundle artifact; readable transpiled code, not obfuscated. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Diff baseline is an old sibling version; size growth is normal bundled build output. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established official Authing package; README/metadata sparsity is not a malware signal here. | ai | |
| source-diff | obfuscated-file:dist/guard/esm2020/lib/guard.component.mjs | AI (source-diff): Readable Angular build output, not true obfuscation. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Standard Angular peer deps for a UI component library. | ai | |
| phantom-deps | phantom-dep:@angular/compiler | AI (phantom-deps): Framework-scoped Angular peer dep; loaded by convention. | ai | |
| phantom-deps | phantom-dep:@angular/animations | AI (phantom-deps): Framework-scoped Angular peer dep; loaded by convention. | ai | |
| phantom-deps | phantom-dep:rxjs | AI (phantom-deps): Angular library peer dep; loaded by convention, not directly imported. | ai | |
| phantom-deps | phantom-dep:@angular/platform-browser-dynamic | AI (phantom-deps): Framework-scoped Angular peer dep; loaded by convention. | ai | |
| phantom-deps | phantom-dep:@angular/platform-browser | AI (phantom-deps): Framework-scoped Angular peer dep; loaded by convention. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): Known implicit TypeScript runtime dep; stable false positive for Angular libraries. | ai | |
| phantom-deps | phantom-dep:zone.js | AI (phantom-deps): Angular peer dep loaded by convention. | ai | |
| phantom-deps | phantom-dep:@angular/forms | AI (phantom-deps): Framework-scoped Angular peer dep; loaded by convention. | ai | |
| phantom-deps | phantom-dep:@angular/common | AI (phantom-deps): Framework-scoped Angular peer dep; loaded by convention. | ai | |
| phantom-deps | phantom-dep:@angular/router | AI (phantom-deps): Framework-scoped Angular peer dep; loaded by convention. | ai |
Versions (showing 51 of 54)
| Version | Deps | Published |
|---|---|---|
| 4.5.54 | 12 / 12 | |
| 4.5.53 | 12 / 12 | |
| 4.5.51 | 12 / 12 | |
| 4.5.50 | 12 / 12 | |
| 4.5.49 | 12 / 12 | |
| 4.5.48 | 12 / 12 | |
| 4.5.47 | 12 / 12 | |
| 4.5.46 | 12 / 12 | |
| 4.5.45 | 12 / 12 | |
| 4.5.44 | 12 / 12 | |
| 4.5.43 | 12 / 12 | |
| 4.5.42 | 12 / 12 | |
| 4.5.41 | 12 / 12 | |
| 4.5.40 | 12 / 12 | |
| 4.5.39 | 12 / 12 | |
| 4.5.37 | 12 / 12 | |
| 4.5.36 | 12 / 12 | |
| 4.5.34 | 12 / 12 | |
| 4.5.33 | 12 / 12 | |
| 4.5.32 | 12 / 12 | |
| 4.5.30 | 12 / 12 | |
| 4.5.29 | 12 / 12 | |
| 4.5.27 | 12 / 12 | |
| 4.5.26 | 12 / 12 | |
| 4.5.25 | 12 / 12 | |
| 4.5.24 | 12 / 12 | |
| 4.5.23 | 12 / 12 | |
| 4.5.19 | 12 / 12 | |
| 4.5.18 | 12 / 12 | |
| 4.5.17 | 12 / 12 | |
| 4.5.16 | 12 / 12 | |
| 4.5.14 | 12 / 12 | |
| 4.5.13 | 12 / 12 | |
| 4.5.12 | 12 / 12 | |
| 4.5.10 | 12 / 12 | |
| 4.5.9 | 12 / 12 | |
| 4.5.8 | 12 / 12 | |
| 4.5.7 | 12 / 12 | |
| 4.5.6 | 12 / 12 | |
| 4.5.5 | 12 / 12 | |
| 4.5.4 | 12 / 12 | |
| 4.5.3 | 12 / 12 | |
| 4.5.1 | 12 / 12 | |
| 4.5.0 | 12 / 12 | |
| 4.3.10 | 2 / 0 | |
| 4.3.8 | 2 / 0 | |
| 4.3.4 | 2 / 0 | |
| 4.3.1 | 2 / 0 | |
| 4.3.0 | 2 / 0 | |
| 4.2.1 | 2 / 0 | |
| 4.2.0 | 2 / 0 |
v4.5.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.17
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.
v4.5.16
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.
v4.5.14
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.
v4.5.13
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.
v4.5.12
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.
v4.5.10
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.
v4.5.9
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.
v4.5.8
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.
v4.5.7
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.
v4.5.6
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.
v4.5.5
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.
v4.5.4
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.
v4.5.3
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.
v4.5.1
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.
v4.5.0
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.
v4.3.10
4 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: authing.
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.
v4.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.1
3 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.
v4.3.0
3 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.
v4.2.1
3 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.
v4.2.0
3 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.