@fundamental-ngx/cx
Fundamental Library for Angular - cx
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:fast-deep-equal | AI (phantom-deps): Angular library config-file reference pattern; consistent with other accepted phantom deps in this package. | ai | |
| dependencies | unvetted-dep:@fundamental-styles/cx | AI (dependencies): Sibling SAP package in the fundamental-ngx ecosystem; consistently used across versions. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a standard Angular/TypeScript implicit runtime dep; stable false positive. | ai | |
| phantom-deps | phantom-dep:lodash-es | AI (phantom-deps): Referenced in config files; standard Angular library packaging pattern. | ai | |
| phantom-deps | phantom-dep:focus-trap | AI (phantom-deps): Referenced in config files; standard Angular library packaging pattern. | ai | |
| phantom-deps | phantom-dep:fast-equals | AI (phantom-deps): Referenced in config files; standard Angular library packaging pattern. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped SAP package; edit-distance match to 'pg' is a false positive. | ai | |
| phantom-deps | phantom-dep:fundamental-styles | AI (phantom-deps): SAP style dependency referenced in config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@fundamental-styles/cx | AI (phantom-deps): SAP style dependency referenced in config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@sap-theming/theming-base-content | AI (phantom-deps): SAP theming dependency referenced in config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:compare-versions | AI (phantom-deps): Referenced in config files; standard Angular library packaging pattern. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped SAP package; edit-distance match to 'qs' is a false positive. | ai |
Versions (showing 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 0.62.3 | 8 / 0 | |
| 0.61.4 | 8 / 0 | |
| 0.61.3 | 8 / 0 | |
| 0.61.2 | 8 / 0 | |
| 0.61.1 | 8 / 0 | |
| 0.61.0 | 8 / 0 | |
| 0.60.2 | 8 / 0 | |
| 0.60.0 | 8 / 0 | |
| 0.59.0 | 8 / 0 | |
| 0.58.6 | 8 / 0 | |
| 0.58.4 | 8 / 0 | |
| 0.58.1 | 8 / 0 | |
| 0.57.12 | 8 / 0 | |
| 0.57.10 | 8 / 0 | |
| 0.57.8 | 8 / 0 | |
| 0.57.5 | 8 / 0 | |
| 0.57.4 | 8 / 0 | |
| 0.57.2 | 8 / 0 | |
| 0.56.9 | 8 / 0 | |
| 0.56.5 | 8 / 0 | |
| 0.56.3 | 8 / 0 | |
| 0.56.1 | 8 / 0 | |
| 0.56.0 | 8 / 0 | |
| 0.55.7 | 8 / 0 | |
| 0.54.4 | 8 / 0 | |
| 0.43.61 | 9 / 0 | |
| 0.43.60 | 9 / 0 | |
| 0.43.57 | 9 / 0 | |
| 0.43.56 | 9 / 0 | |
| 0.43.54 | 9 / 0 |
v0.62.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.61.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.61.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.61.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.61.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.61.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.60.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.60.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.59.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.58.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.58.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.58.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.57.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.57.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.57.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.57.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.57.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.57.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.56.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.56.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.56.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.56.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.56.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.55.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.54.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.61
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.60
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.57
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.