@ng-icons/core
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped Angular icon library; name similarity to 'cors' is coincidental and not a typosquat. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a standard Angular/TypeScript build dependency; implicit usage is expected. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 33.2.3 | 1 / 0 | |
| 33.2.2 | 1 / 0 | |
| 33.2.1 | 1 / 0 | |
| 33.2.0 | 1 / 0 | |
| 33.1.0 | 1 / 0 | |
| 33.0.1 | 1 / 0 | |
| 33.0.0 | 1 / 0 | |
| 32.5.0 | 1 / 0 | |
| 32.4.0 | 1 / 0 | |
| 32.3.0 | 1 / 0 |
v33.2.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v33.2.1
2 findingsPackage name '@ng-icons/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v33.2.0
2 findingsPackage name '@ng-icons/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v33.1.0
2 findingsPackage name '@ng-icons/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v33.0.1
2 findingsPackage name '@ng-icons/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v33.0.0
2 findingsPackage name '@ng-icons/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v32.5.0
2 findingsPackage name '@ng-icons/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v32.4.0
2 findingsPackage name '@ng-icons/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v32.3.0
2 findingsPackage name '@ng-icons/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.