@onecx/shell-core
This library was generated with [Nx](https://nx.dev).
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:esm2022/lib/shell-interface/workspace-config-bff-service-provider.mjs | AI (source-diff): Long line is a base64 sourceMappingURL comment, standard Angular build artifact. | ai | |
| source-diff | obfuscated-file:esm2022/lib/shell-core.module.mjs | AI (source-diff): Angular compiler output with inline templates; long lines are normal for this build format. | ai | |
| source-diff | obfuscated-file:esm2022/lib/directives/src.directive.mjs | AI (source-diff): Angular compiler output; long lines from sourceMappingURL base64 data, not obfuscation. | ai | |
| source-diff | obfuscated-file:esm2022/lib/components/error-component/global-error.component.mjs | AI (source-diff): Angular compiler output with inline templates; long lines are normal for this build format. | ai | |
| source-diff | obfuscated-file:esm2022/lib/components/portal-header/header.component.mjs | AI (source-diff): Angular compiler output with inline templates; long lines are normal for this build format. | ai | |
| source-diff | obfuscated-file:esm2022/lib/components/portal-footer/portal-footer.component.mjs | AI (source-diff): Angular compiler output with inline templates; long lines are normal for this build format. | ai | |
| source-diff | obfuscated-file:esm2022/lib/components/portal-viewport/portal-viewport.component.mjs | AI (source-diff): Angular compiler output with inline templates; long lines are normal for this build format. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established Angular library with 260 versions; sparse README/keywords are cosmetic, not spam indicators. | ai | |
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions publisher with SLSA attestation is the documented CI/CD release pattern for this org. | ai |
Versions (showing 51 of 64)
| Version | Deps | Published |
|---|---|---|
| 6.24.0 | 1 / 0 | |
| 6.23.2 | 1 / 0 | |
| 6.23.1 | 1 / 0 | |
| 6.23.0 | 1 / 0 | |
| 6.22.1 | 1 / 0 | |
| 6.22.0 | 1 / 0 | |
| 6.21.1 | 1 / 0 | |
| 6.21.0 | 1 / 0 | |
| 6.20.0 | 1 / 0 | |
| 6.19.0 | 1 / 0 | |
| 6.18.0 | 1 / 0 | |
| 6.17.0 | 1 / 0 | |
| 6.16.1 | 1 / 0 | |
| 6.16.0 | 1 / 0 | |
| 6.15.1 | 1 / 0 | |
| 6.15.0 | 1 / 0 | |
| 6.14.4 | 1 / 0 | |
| 6.14.3 | 1 / 0 | |
| 6.14.2 | 1 / 0 | |
| 6.14.1 | 1 / 0 | |
| 6.14.0 | 1 / 0 | |
| 6.13.2 | 1 / 0 | |
| 6.13.1 | 1 / 0 | |
| 6.13.0 | 1 / 0 | |
| 6.12.2 | 1 / 0 | |
| 6.12.1 | 1 / 0 | |
| 6.12.0 | 1 / 0 | |
| 6.11.1 | 1 / 0 | |
| 6.11.0 | 1 / 0 | |
| 6.10.0 | 1 / 0 | |
| 6.9.0 | 1 / 0 | |
| 6.8.1 | 1 / 0 | |
| 6.8.0 | 1 / 0 | |
| 6.7.0 | 1 / 0 | |
| 6.6.0 | 1 / 0 | |
| 6.5.3 | 1 / 0 | |
| 6.5.2 | 1 / 0 | |
| 6.5.1 | 1 / 0 | |
| 6.5.0 | 1 / 0 | |
| 6.4.0 | 1 / 0 | |
| 6.3.0 | 1 / 0 | |
| 6.2.1 | 1 / 0 | |
| 6.2.0 | 1 / 0 | |
| 6.1.0 | 1 / 0 | |
| 6.0.0 | 1 / 0 | |
| 5.57.0 | 1 / 0 | |
| 5.56.0 | 1 / 0 | |
| 5.55.0 | 1 / 0 | |
| 5.54.0 | 1 / 0 | |
| 5.53.1 | 1 / 0 | |
| 5.53.0 | 1 / 0 |
v6.24.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.23.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.23.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.23.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.22.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.22.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.21.1
2 findingsThis version was published by a different npm account than previous versions on 2026-04-29. 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.
v6.21.0
2 findingsThis version was published by a different npm account than previous versions on 2026-04-28. 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.
v6.20.0
2 findingsThis version was published by a different npm account than previous versions on 2026-04-22. 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.
v6.19.0
2 findingsThis version was published by a different npm account than previous versions on 2026-04-02. 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.
v6.18.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.17.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.16.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.16.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.15.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.15.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.14.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.14.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.14.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.14.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.14.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.13.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.13.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.13.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.12.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.12.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.12.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.11.1
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version was published by a different npm account than previous versions on 2025-12-15. This could indicate a legitimate maintainer transition or an account compromise.
v6.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.57.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.56.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.54.0
9 findingsThis version was published by a different npm account than previous versions on 2026-04-02. This could indicate a legitimate maintainer transition or an account compromise.
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.
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.
Newly 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.
v5.53.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.53.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.