@progress-chef/platform-http-interceptor
This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 16.2.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:esm2022/lib/http-auth.interceptor.mjs | AI (source-diff): Angular library ESM output; code is readable Angular interceptor logic, not obfuscated. | ai |
Versions (showing 15 of 15)
| 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.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 |
v1.0.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.33
3 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.
This version was published by a different npm account (anees-progress) than the most recent previously approved version (vaigadre19) on 2026-02-06, 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.32
3 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.
This version was published by a different npm account (anees-progress) than the most recent previously approved version (vaigadre19) on 2026-01-27, 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.31
3 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.
This version was published by a different npm account (anees-progress) than the most recent previously approved version (vaigadre19) on 2026-01-16, 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.30
3 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.
This version was published by a different npm account (anees-progress) than the most recent previously approved version (vaigadre19) on 2026-01-16, 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.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.