@eqproject/eqp-lookup
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/directives/dynamic-loader/dynamic-loader.directive.mjs | AI (source-diff): Long lines are Angular compiled metadata (ɵɵngDeclare*), not obfuscation. Stable pattern for this Angular library. | ai | |
| source-diff | obfuscated-file:esm2022/lib/eqp-lookup.component.mjs | AI (source-diff): Long lines are Angular compiled metadata (ɵɵngDeclare*), not obfuscation. Stable pattern for this Angular library. | ai | |
| source-diff | obfuscated-file:esm2022/lib/eqp-lookup.service.mjs | AI (source-diff): Long lines are Angular compiled metadata (ɵɵngDeclare*), not obfuscation. Stable pattern for this Angular library. | ai | |
| source-diff | obfuscated-file:lib/eqp-lookup.component.d.ts | AI (source-diff): TypeScript declaration file with long lines from Angular metadata; not obfuscation. Stable pattern for this Angular library. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a standard Angular/TypeScript runtime dep; implicit usage is expected in compiled Angular libraries. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 21.0.1 | 1 / 0 | |
| 21.0.0 | 1 / 0 | |
| 3.0.13 | 1 / 0 | |
| 3.0.12 | 1 / 0 | |
| 3.0.11 | 1 / 0 | |
| 3.0.10 | 1 / 0 | |
| 3.0.9 | 1 / 0 | |
| 3.0.8 | 1 / 0 | |
| 3.0.7 | 1 / 0 | |
| 3.0.6 | 1 / 0 | |
| 3.0.5 | 1 / 0 |
v21.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.12
5 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.