@huntsman-cancer-institute/angular-tree-component
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/angular-tree-component/esm2020/lib/models/tree.model.mjs | AI (source-diff): Angular Ivy ESM output with inlined sourcemap; stable false positive. | ai | |
| source-diff | obfuscated-file:dist/angular-tree-component/esm2020/lib/models/tree-node.model.mjs | AI (source-diff): Angular Ivy ESM output with inlined sourcemap; stable false positive. | ai | |
| source-diff | obfuscated-file:dist/angular-tree-component/esm2020/lib/models/tree-options.model.mjs | AI (source-diff): Angular Ivy ESM output with inlined sourcemap; stable false positive. | ai | |
| source-diff | obfuscated-file:dist/angular-tree-component/esm2020/lib/components/tree-viewport.component.mjs | AI (source-diff): Angular Ivy ESM output with inlined sourcemap; stable false positive. | ai | |
| source-diff | obfuscated-file:dist/angular-tree-component/esm2020/lib/models/tree-virtual-scroll.model.mjs | AI (source-diff): Angular Ivy ESM output with inlined sourcemap; stable false positive. | ai | |
| source-diff | obfuscated-file:dist/angular-tree-component/esm2020/lib/components/tree.component.mjs | AI (source-diff): Angular Ivy ESM output with inlined sourcemap; stable false positive. | ai | |
| source-diff | obfuscated-file:dist/angular-tree-component/esm2020/lib/angular-tree-component.module.mjs | AI (source-diff): Long lines are Angular Ivy compiler output with inlined base64 sourcemaps; stable false positive for this package. | ai | |
| source-diff | obfuscated-file:dist/angular-tree-component/esm2020/lib/defs/api.mjs | AI (source-diff): File is a type-only export with an inlined base64 sourcemap; not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/angular-tree-component/esm2020/lib/directives/tree-animate-open.directive.mjs | AI (source-diff): Angular Ivy ESM output with inlined sourcemap; stable false positive. | ai | |
| source-diff | obfuscated-file:dist/angular-tree-component/esm2020/lib/directives/tree-drag.directive.mjs | AI (source-diff): Angular Ivy ESM output with inlined sourcemap; stable false positive. | ai | |
| source-diff | obfuscated-file:dist/angular-tree-component/esm2020/lib/directives/tree-drop.directive.mjs | AI (source-diff): Angular Ivy ESM output with inlined sourcemap; stable false positive. | ai | |
| source-diff | obfuscated-file:dist/angular-tree-component/esm2020/lib/mobx-angular/tree-mobx-autorun.directive.mjs | AI (source-diff): Angular Ivy ESM output with inlined sourcemap; stable false positive. | ai | |
| source-diff | obfuscated-file:dist/angular-tree-component/esm2020/lib/components/tree-node-collection.component.mjs | AI (source-diff): Angular Ivy ESM output with inlined sourcemap; stable false positive. | ai | |
| source-diff | obfuscated-file:dist/angular-tree-component/esm2020/lib/components/tree-node-wrapper.component.mjs | AI (source-diff): Angular Ivy ESM output with inlined sourcemap; stable false positive. | ai | |
| phantom-deps | phantom-dep:@angular/cdk | AI (phantom-deps): Angular framework package; loaded by convention in Angular apps. | ai | |
| phantom-deps | phantom-dep:@angular/forms | AI (phantom-deps): Angular framework package; loaded by convention in Angular apps. | ai | |
| phantom-deps | phantom-dep:@angular/material | AI (phantom-deps): Angular framework package; loaded by convention in Angular apps. | ai | |
| phantom-deps | phantom-dep:@angular/animations | AI (phantom-deps): Angular framework package; loaded by convention in Angular apps. | ai | |
| phantom-deps | phantom-dep:core-js | AI (phantom-deps): Runtime polyfill; stable implicit dependency for Angular projects. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 13.3.10 | 2 / 0 | |
| 13.3.9 | 2 / 0 | |
| 13.3.8 | 2 / 0 | |
| 13.3.7 | 2 / 0 | |
| 13.3.6 | 2 / 0 | |
| 13.3.5 | 2 / 0 | |
| 13.3.4 | 2 / 0 | |
| 13.3.3 | 2 / 0 | |
| 13.3.2 | 2 / 0 | |
| 13.3.1 | 2 / 0 | |
| 13.3.0 | 6 / 46 | |
| 13.2.1 | 2 / 0 | |
| 13.2.0 | 6 / 46 | |
| 13.1.4 | 6 / 46 | |
| 13.1.3 | 6 / 46 | |
| 13.1.2 | 2 / 0 | |
| 13.1.1 | 2 / 0 | |
| 13.1.0 | 2 / 0 |
v13.3.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.2.0
15 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.
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.
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.
v13.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.