@huntsman-cancer-institute/help

This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 12.2.0.

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

npluspluslddenyshcihdusersarveshjainu0493164

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	obfuscated-file:fesm5/huntsman-cancer-institute-help.js	AI (source-diff): Standard Angular fesm5 bundle output; long lines are expected.	ai	2026/05/15
source-diff	obfuscated-file:esm5/help.component.js	AI (source-diff): Standard Angular esm5 build output.	ai	2026/05/15
source-diff	obfuscated-file:esm2015/help.entity.js	AI (source-diff): Standard Angular esm2015 build output.	ai	2026/05/15
source-diff	obfuscated-file:esm5/help.entity.js	AI (source-diff): Standard Angular esm5 build output.	ai	2026/05/15
source-diff	obfuscated-file:esm2015/help.service.js	AI (source-diff): Standard Angular esm2015 build output.	ai	2026/05/15
source-diff	obfuscated-file:esm5/help.service.js	AI (source-diff): Standard Angular esm5 build output.	ai	2026/05/15
source-diff	obfuscated-file:esm2015/help-cache.class.js	AI (source-diff): Standard Angular esm2015 build output; long lines are minified bundle format, not obfuscation.	ai	2026/05/15
source-diff	obfuscated-file:esm5/help-cache.class.js	AI (source-diff): Standard Angular esm5 build output; long lines are minified bundle format, not obfuscation.	ai	2026/05/15
source-diff	obfuscated-file:esm2015/help.component.js	AI (source-diff): Standard Angular esm2015 build output.	ai	2026/05/15
source-diff	obfuscated-file:esm2022/help.component.mjs	AI (source-diff): Angular ESM2022 compiled output; long lines are ɵfac/ɵcmp metadata, not obfuscation.	ai	2026/05/15
source-diff	obfuscated-file:esm2022/help.entity.mjs	AI (source-diff): Angular ESM2022 compiled output; long lines are ɵfac/ɵcmp metadata, not obfuscation.	ai	2026/05/15
source-diff	obfuscated-file:esm2022/help.service.mjs	AI (source-diff): Angular ESM2022 compiled output; long lines are ɵfac/ɵcmp metadata, not obfuscation.	ai	2026/05/15
phantom-deps	phantom-dep:tslib	AI (phantom-deps): tslib is a known implicit Angular/TypeScript runtime dep; stable false positive for this package.	ai	2026/05/15
source-diff	obfuscated-file:esm2022/help-cache.class.mjs	AI (source-diff): Angular ESM2022 compiled output; long lines are ɵfac/ɵcmp metadata, not obfuscation.	ai	2026/05/15

Versions (showing 71 of 71)

Version	Deps	Published
17.24.0	3 / 0	2026-06-08
17.23.8	3 / 0	2026-05-19
17.23.7	3 / 0	2026-04-28
17.23.6	3 / 0	2026-04-24
17.23.5	3 / 0	2026-04-22
17.23.4	3 / 0	2026-04-15
17.23.3	3 / 0	2026-04-15
17.23.2	3 / 0	2026-04-10
17.23.1	3 / 0	2026-04-10
17.23.0	3 / 0	2026-04-10
17.22.0	3 / 0	2026-04-08
17.21.1	3 / 0	2026-04-07
17.21.0	3 / 0	2026-04-06
17.20.8	3 / 0	2026-04-01
17.20.7	3 / 0	2026-04-01
17.20.6	3 / 0	2026-03-26
17.20.5	3 / 0	2026-03-24
17.20.0	3 / 0	2026-03-22
17.19.0	3 / 0	2026-03-20
17.18.4	3 / 0	2026-03-18
17.18.3	3 / 0	2026-03-16
17.18.2	3 / 0	2026-02-27
17.18.1	3 / 0	2026-02-27
17.18.0	3 / 0	2026-02-24
17.17.6	3 / 0	2026-02-12
17.17.5	3 / 0	2026-02-12
17.17.4	3 / 0	2026-02-12
17.17.3	3 / 0	2026-02-11
17.17.2	3 / 0	2026-02-10
17.17.0	3 / 0	2026-02-05
17.16.1	3 / 0	2026-02-05
17.16.0	3 / 0	2026-02-03
17.15.1	3 / 0	2026-01-26
17.15.0	3 / 0	2026-01-23
17.14.6	3 / 0	2026-01-22
17.14.5	3 / 0	2026-01-16
17.14.4	3 / 0	2026-01-08
17.14.3	3 / 0	2026-01-05
17.14.2	3 / 0	2025-12-16
17.14.1	3 / 0	2025-12-11
17.14.0	3 / 0	2025-12-04
17.13.0	3 / 0	2025-11-26
17.12.0	3 / 0	2025-11-24
17.11.7	3 / 0	2025-11-18
17.11.6	3 / 0	2025-10-24
17.11.5	3 / 0	2025-10-16
17.11.4	3 / 0	2025-10-14
17.11.3	3 / 0	2025-10-14
17.11.1	3 / 0	2025-10-06
17.11.0	3 / 0	2025-09-25
17.10.4	3 / 0	2025-09-23
17.10.3	3 / 0	2025-09-19
17.10.2	3 / 0	2025-09-17
17.10.1	3 / 0	2025-09-15
17.10.0	3 / 0	2025-09-09
17.9.6	3 / 0	2025-08-18
17.9.5	3 / 0	2025-08-11
17.9.4	3 / 0	2025-08-08
17.9.3	3 / 0	2025-08-01
17.9.2	3 / 0	2025-07-28
17.9.1	3 / 0	2025-07-21
17.9.0	3 / 0	2025-07-11
17.8.1	3 / 0	2025-06-30
17.8.0	3 / 0	2025-06-17
17.7.5	3 / 0	2025-06-09
17.7.4	3 / 0	2025-06-04
17.7.3	3 / 0	2025-05-07
17.7.2	3 / 0	2025-05-01
12.14.1	3 / 0	2026-04-06
12.14.0	3 / 0	2026-04-01
12.13.3	3 / 0	2026-03-20

v17.24.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v17.23.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v17.23.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v17.23.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v17.23.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v17.23.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v17.23.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v17.23.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v17.23.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v17.23.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v17.22.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v17.21.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v17.21.0

5 findings

HIGH New obfuscated file: esm2022/help-cache.class.mjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: esm2022/help.component.mjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: esm2022/help.entity.mjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: esm2022/help.service.mjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v17.20.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v17.20.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v17.20.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v17.20.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v17.20.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v17.19.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v17.18.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v17.18.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v17.18.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v17.18.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v17.18.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v17.17.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v17.17.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v17.17.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v17.17.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v17.17.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v17.17.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v17.16.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v17.16.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v17.15.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v17.15.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v17.14.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v17.14.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v17.14.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v17.14.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v17.14.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v17.14.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v17.14.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v17.13.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v17.12.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v17.11.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v17.11.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v17.11.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v17.11.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v17.11.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v17.11.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v17.11.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v17.10.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v17.10.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v17.10.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v17.10.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v17.10.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v17.9.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v17.9.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v17.9.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v17.9.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v17.9.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v17.9.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v17.9.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v17.8.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v17.8.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v17.7.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v17.7.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v17.7.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v17.7.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v12.14.1

11 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nplusplus.

HIGH New obfuscated file: esm2015/help-cache.class.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: esm5/help-cache.class.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: esm2015/help.component.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: esm5/help.component.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: esm2015/help.entity.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: esm5/help.entity.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: esm2015/help.service.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: esm5/help.service.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: fesm5/huntsman-cancer-institute-help.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v12.14.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v12.13.3