@fundamental-ngx/btp
Fundamental Library for Angular - BTP
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): SAP/fundamental-ngx migrated to GitHub Actions CI publishing with SLSA attestation; this is a documented, legitimate transition. | ai | |
| source-diff | obfuscated-file:esm2022/navigation/index.mjs | AI (source-diff): Long lines are Angular compiler inline base64 sourcemaps, not obfuscation. Stable pattern for this Angular component library. | ai | |
| source-diff | obfuscated-file:esm2022/navigation/models/navigation-content-container.class.mjs | AI (source-diff): Angular compiler inline sourcemap; not obfuscated code. | ai | |
| source-diff | obfuscated-file:esm2022/navigation/components/navigation-end/navigation-content-end.component.mjs | AI (source-diff): Angular compiler inline sourcemap; not obfuscated code. | ai | |
| source-diff | obfuscated-file:esm2022/navigation/components/navigation-start/navigation-content-start.component.mjs | AI (source-diff): Angular compiler inline sourcemap; not obfuscated code. | ai | |
| source-diff | obfuscated-file:esm2022/navigation/models/navigation-data-source-item.model.mjs | AI (source-diff): Angular compiler inline sourcemap; not obfuscated code. | ai | |
| source-diff | obfuscated-file:esm2022/navigation/components/navigation-link/navigation-link.component.mjs | AI (source-diff): Angular compiler inline sourcemap; not obfuscated code. | ai | |
| source-diff | obfuscated-file:esm2022/navigation/directives/navigation-list-item-ref.directive.mjs | AI (source-diff): Angular compiler inline sourcemap; not obfuscated code. | ai | |
| source-diff | obfuscated-file:esm2022/navigation/models/navigation-list-item.class.mjs | AI (source-diff): Angular compiler inline sourcemap; not obfuscated code. | ai | |
| source-diff | obfuscated-file:esm2022/navigation/components/navigation-list/navigation-list.component.mjs | AI (source-diff): Angular compiler inline sourcemap; not obfuscated code. | ai | |
| source-diff | obfuscated-file:esm2022/navigation-menu/lib/navigation-menu-item.component.mjs | AI (source-diff): Angular compiler inline sourcemap; not obfuscated code. | ai | |
| source-diff | obfuscated-file:esm2022/navigation-menu/lib/navigation-menu.component.mjs | AI (source-diff): Angular compiler inline sourcemap; not obfuscated code. | ai | |
| source-diff | obfuscated-file:esm2022/navigation/components/navigation-more-button/navigation-more-button.component.mjs | AI (source-diff): Angular compiler inline sourcemap; not obfuscated code. | ai | |
| source-diff | obfuscated-file:esm2022/navigation/components/navigation/navigation.component.mjs | AI (source-diff): Angular compiler inline sourcemap; not obfuscated code. | ai | |
| source-diff | obfuscated-file:esm2022/search-field/search-field.component.mjs | AI (source-diff): Angular compiler inline sourcemap; not obfuscated code. | ai | |
| source-diff | obfuscated-file:esm2022/splitter/splitter-pagination/splitter-pagination.component.mjs | AI (source-diff): Angular compiler inline sourcemap; not obfuscated code. | ai | |
| source-diff | obfuscated-file:esm2022/splitter/splitter-pane-container/splitter-pane-container.component.mjs | AI (source-diff): Angular compiler inline sourcemap; not obfuscated code. | ai | |
| source-diff | obfuscated-file:esm2022/navigation/components/navigation-item/navigation-list-item.component.mjs | AI (source-diff): Angular compiler inline sourcemap; not obfuscated code. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Established SAP Angular library; no relation to 'yup'. Levenshtein match is a false positive. | ai |
Versions (showing 51 of 57)
| Version | Deps | Published |
|---|---|---|
| 0.62.3 | 1 / 0 | |
| 0.62.2 | 1 / 0 | |
| 0.62.1 | 1 / 0 | |
| 0.62.0 | 1 / 0 | |
| 0.61.5 | 1 / 0 | |
| 0.61.4 | 1 / 0 | |
| 0.61.3 | 1 / 0 | |
| 0.61.2 | 1 / 0 | |
| 0.61.1 | 1 / 0 | |
| 0.61.0 | 1 / 0 | |
| 0.60.3 | 1 / 0 | |
| 0.60.2 | 1 / 0 | |
| 0.60.1 | 1 / 0 | |
| 0.60.0 | 1 / 0 | |
| 0.59.3 | 1 / 0 | |
| 0.59.2 | 1 / 0 | |
| 0.59.1 | 1 / 0 | |
| 0.59.0 | 1 / 0 | |
| 0.58.6 | 1 / 0 | |
| 0.58.5 | 1 / 0 | |
| 0.58.4 | 1 / 0 | |
| 0.58.3 | 1 / 0 | |
| 0.58.2 | 1 / 0 | |
| 0.58.1 | 1 / 0 | |
| 0.58.0 | 1 / 0 | |
| 0.57.12 | 1 / 0 | |
| 0.57.11 | 1 / 0 | |
| 0.57.10 | 1 / 0 | |
| 0.57.9 | 1 / 0 | |
| 0.57.8 | 1 / 0 | |
| 0.57.7 | 1 / 0 | |
| 0.57.6 | 1 / 0 | |
| 0.57.5 | 1 / 0 | |
| 0.57.4 | 1 / 0 | |
| 0.57.3 | 1 / 0 | |
| 0.57.2 | 1 / 0 | |
| 0.57.1 | 1 / 0 | |
| 0.57.0 | 1 / 0 | |
| 0.56.9 | 1 / 0 | |
| 0.56.8 | 1 / 0 | |
| 0.56.7 | 1 / 0 | |
| 0.56.6 | 1 / 0 | |
| 0.56.5 | 1 / 0 | |
| 0.56.4 | 1 / 0 | |
| 0.56.3 | 1 / 0 | |
| 0.56.2 | 1 / 0 | |
| 0.56.1 | 1 / 0 | |
| 0.56.0 | 1 / 0 | |
| 0.55.10 | 1 / 0 | |
| 0.55.9 | 1 / 0 | |
| 0.55.8 | 1 / 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.2
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.62.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.61.5
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
2 findingsThis version was published by a different npm account than previous versions on 2026-03-31. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.61.2
2 findingsThis version was published by a different npm account than previous versions on 2026-03-13. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.61.1
2 findingsThis version was published by a different npm account than previous versions on 2026-03-06. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.61.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-05. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.60.3
2 findingsThis version was published by a different npm account than previous versions on 2026-03-06. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.60.2
2 findingsThis version was published by a different npm account than previous versions on 2026-03-03. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.60.1
2 findingsThis version was published by a different npm account than previous versions on 2026-02-24. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.60.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-17. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.59.3
2 findingsThis version was published by a different npm account than previous versions on 2026-03-06. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.59.2
2 findingsThis version was published by a different npm account than previous versions on 2026-03-03. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.59.1
2 findingsThis version was published by a different npm account than previous versions on 2026-02-05. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.59.0
2 findingsThis version was published by a different npm account than previous versions on 2026-01-24. This could indicate a legitimate maintainer transition or an account compromise.
Published 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.5
2 findingsThis version was published by a different npm account than previous versions on 2026-03-16. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.58.4
2 findingsThis version was published by a different npm account than previous versions on 2026-03-12. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.58.3
2 findingsThis version was published by a different npm account than previous versions on 2026-03-06. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.58.2
2 findingsThis version was published by a different npm account than previous versions on 2026-02-20. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.58.1
2 findingsThis version was published by a different npm account than previous versions on 2026-01-21. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.58.0
2 findingsThis version was published by a different npm account than previous versions on 2026-01-19. This could indicate a legitimate maintainer transition or an account compromise.
Published 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. Consider requesting the maintainer enable provenance via CI/CD.
v0.57.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.57.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.57.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.57.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.57.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.57.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.57.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.57.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.57.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.56.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.56.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.56.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.56.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.56.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.56.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.55.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.55.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.