@fundamental-ngx/cdk
Fundamental Library for Angular - CDK
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:utils/index.d.ts | AI (source-diff): TypeScript declaration files for Angular libraries produce long lines from complex type unions; not obfuscation. | ai | |
| phantom-deps | phantom-dep:@fundamental-ngx/i18n | AI (phantom-deps): Same-org sibling dep; phantom detection is a false positive here. | ai | |
| dependencies | unvetted-dep:@fundamental-styles/cx | AI (dependencies): SAP sibling package in the fundamental-styles ecosystem; stable dependency across versions. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a well-known Angular/TypeScript implicit runtime dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:lodash-es | AI (phantom-deps): Angular library; lodash-es likely tree-shaken/used indirectly in build output, stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@sap-theming/theming-base-content | AI (phantom-deps): SAP theming asset dep; referenced in config, stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:compare-versions | AI (phantom-deps): Declared dep used in build/config context; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:fundamental-styles | AI (phantom-deps): First-party SAP styling dep; referenced in config/styles, stable false positive. | ai | |
| phantom-deps | phantom-dep:@fundamental-styles/cx | AI (phantom-deps): First-party SAP styling dep; referenced in config/styles, stable false positive. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 0.62.3 | 8 / 0 | |
| 0.62.1 | 8 / 0 | |
| 0.61.3 | 8 / 0 | |
| 0.61.2 | 8 / 0 | |
| 0.60.3 | 8 / 0 | |
| 0.59.1 | 8 / 0 | |
| 0.58.6 | 8 / 0 | |
| 0.57.10 | 8 / 0 | |
| 0.57.9 | 8 / 0 | |
| 0.57.4 | 8 / 0 | |
| 0.57.3 | 8 / 0 | |
| 0.57.2 | 8 / 0 | |
| 0.57.1 | 8 / 0 | |
| 0.57.0 | 8 / 0 | |
| 0.56.8 | 8 / 0 | |
| 0.56.6 | 8 / 0 | |
| 0.56.5 | 8 / 0 | |
| 0.56.3 | 8 / 0 | |
| 0.55.8 | 8 / 0 | |
| 0.55.7 | 8 / 0 | |
| 0.54.6 | 8 / 0 | |
| 0.54.4 | 8 / 0 | |
| 0.53.5 | 8 / 0 | |
| 0.53.4 | 8 / 0 | |
| 0.43.61 | 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.62.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.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.60.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.59.1
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
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
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.9
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.3
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.57.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.57.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.56.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.56.6
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.55.8
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.6
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.53.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.53.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.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.