← Home

@progress-chef/platform-http-interceptor

npm

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

41
Versions
Apache-2.0
License
No
Install Scripts
Missing
Provenance

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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

bwloomisagmathurvaigadre19kasif-adnanvinaysharma033arunjn-progressanees-progress

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:tslib AI (phantom-deps): tslib is a standard implicit runtime dep for TS-compiled Angular libs. ai
source-diff obfuscated-file:esm2022/lib/http-auth.interceptor.mjs AI (source-diff): Angular library ESM output; code is readable Angular interceptor logic, not obfuscated. ai

Versions (showing 41 of 41)

Version Deps Published
1.0.42 1 / 0
1.0.41 1 / 0
1.0.40 1 / 0
1.0.39 1 / 0
1.0.37 1 / 0
1.0.35 1 / 0
1.0.34 1 / 0
1.0.33 1 / 0
1.0.32 1 / 0
1.0.31 1 / 0
1.0.30 1 / 0
1.0.29 1 / 0
1.0.28 1 / 0
1.0.27 1 / 0
1.0.26 1 / 0
1.0.25 1 / 0
1.0.24 1 / 0
1.0.23 1 / 0
1.0.22 1 / 0
1.0.21 1 / 0
1.0.20 1 / 0
1.0.19 1 / 0
1.0.18 1 / 0
1.0.17 1 / 0
1.0.16 1 / 0
1.0.15 1 / 0
1.0.14 1 / 0
1.0.13 1 / 0
1.0.12 1 / 0
1.0.11 3 / 0
1.0.10 3 / 0
1.0.9 3 / 0
1.0.8 3 / 0
1.0.7 3 / 0
1.0.6 3 / 0
1.0.5 3 / 0
1.0.4 3 / 0
1.0.3 3 / 0
1.0.2 3 / 0
1.0.1 3 / 0
1.0.0 3 / 0

v1.0.35

2 findings
HIGH Publisher changed: anees-progress → GitHub Actions (on 2026-02-18) provenance

This version was published by a different npm account than previous versions on 2026-02-18. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v1.0.34

2 findings
HIGH Publisher changed: anees-progress → GitHub Actions (on 2026-02-09) provenance

This version was published by a different npm account than previous versions on 2026-02-09. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v1.0.23

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: arunjn-progress → vaigadre19 (on 2025-04-16, known maintainer) provenance

This version was published by a different npm account (vaigadre19) than the most recent previously approved version (arunjn-progress) on 2025-04-16, but vaigadre19 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.0.22

1 finding
LOW No provenance attestation provenance

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

v1.0.21

1 finding
LOW No provenance attestation provenance

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

v1.0.20

1 finding
LOW No provenance attestation provenance

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

v1.0.19

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: vinaysharma033 → arunjn-progress (on 2025-04-15, known maintainer) provenance

This version was published by a different npm account (arunjn-progress) than the most recent previously approved version (vinaysharma033) on 2025-04-15, but arunjn-progress is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.0.18

1 finding
LOW No provenance attestation provenance

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

v1.0.17

1 finding
LOW No provenance attestation provenance

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

v1.0.16

1 finding
LOW No provenance attestation provenance

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

v1.0.15

1 finding
LOW No provenance attestation provenance

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

v1.0.14

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: vaigadre19 → vinaysharma033 (on 2025-03-20, known maintainer) provenance

This version was published by a different npm account (vinaysharma033) than the most recent previously approved version (vaigadre19) on 2025-03-20, but vinaysharma033 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.0.13

1 finding
LOW No provenance attestation provenance

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

v1.0.12

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.

v1.0.11

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: anees-progress → vaigadre19 (on 2025-02-07, known maintainer) provenance

This version was published by a different npm account (vaigadre19) than the most recent previously approved version (anees-progress) on 2025-02-07, but vaigadre19 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.0.10

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: arunjn-progress → anees-progress (on 2025-02-07, known maintainer) provenance

This version was published by a different npm account (anees-progress) than the most recent previously approved version (arunjn-progress) on 2025-02-07, but anees-progress is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.0.9

1 finding
LOW No provenance attestation provenance

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

v1.0.8

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: vinaysharma033 → arunjn-progress (on 2025-01-20, known maintainer) provenance

This version was published by a different npm account (arunjn-progress) than the most recent previously approved version (vinaysharma033) on 2025-01-20, but arunjn-progress is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.0.7

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: vinaysharma033 → vaigadre19 (on 2025-01-10, known maintainer) provenance

This version was published by a different npm account (vaigadre19) than the most recent previously approved version (vinaysharma033) on 2025-01-10, but vaigadre19 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.0.6

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: vaigadre19 → vinaysharma033 (on 2025-01-08, known maintainer) provenance

This version was published by a different npm account (vinaysharma033) than the most recent previously approved version (vaigadre19) on 2025-01-08, but vinaysharma033 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.0.5

1 finding
LOW No provenance attestation provenance

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

v1.0.4

1 finding
LOW No provenance attestation provenance

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

v1.0.3

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: agmathur → vaigadre19 (on 2024-12-24, known maintainer) provenance

This version was published by a different npm account (vaigadre19) than the most recent previously approved version (agmathur) on 2024-12-24, but vaigadre19 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.0.2

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: agmathur → vaigadre19 (on 2024-12-09, known maintainer) provenance

This version was published by a different npm account (vaigadre19) than the most recent previously approved version (agmathur) on 2024-12-09, but vaigadre19 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.0.1

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.

v1.0.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.