@onecx/angular-testing
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI publisher with SLSA attestation; consistent with org-level automation adoption. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainer added alongside CI automation shift; consistent with legitimate org transition. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established library in onecx org; sparse README is a style choice, not a spam indicator. | ai | |
| source-diff | obfuscated-file:esm2022/lib/harnesses/input.harness.mjs | AI (source-diff): Inline sourcemap only; code is plaintext. | ai | |
| source-diff | obfuscated-file:esm2022/lib/harnesses/primeng/p-button-directive.harness.mjs | AI (source-diff): Inline sourcemap only; code is plaintext. | ai | |
| source-diff | obfuscated-file:esm2022/lib/harnesses/primeng/p-button.harness.mjs | AI (source-diff): Inline sourcemap only; code is plaintext. | ai | |
| source-diff | obfuscated-file:esm2022/lib/harnesses/primeng/p-checkbox.harness.mjs | AI (source-diff): Inline sourcemap only; code is plaintext. | ai | |
| source-diff | obfuscated-file:esm2022/lib/harnesses/primeng/p-dropdown.harness.mjs | AI (source-diff): Inline sourcemap only; code is plaintext. | ai | |
| source-diff | obfuscated-file:esm2022/lib/harnesses/primeng/p-menu.harness.mjs | AI (source-diff): Inline sourcemap only; code is plaintext. | ai | |
| source-diff | obfuscated-file:esm2022/lib/harnesses/primeng/p-multiSelect.harness.mjs | AI (source-diff): Inline sourcemap only; code is plaintext. | ai | |
| source-diff | obfuscated-file:esm2022/lib/harnesses/button.harness.mjs | AI (source-diff): Long line is a standard Angular inline sourcemap (base64); code is fully readable above it. | ai | |
| source-diff | obfuscated-file:esm2022/lib/harnesses/primeng/p-picklist.harness.mjs | AI (source-diff): Inline sourcemap only; code is plaintext. | ai | |
| source-diff | obfuscated-file:esm2022/lib/harnesses/p.harness.mjs | AI (source-diff): Inline sourcemap only; code is plaintext. | ai | |
| source-diff | obfuscated-file:esm2022/lib/harnesses/span.harness.mjs | AI (source-diff): Inline sourcemap only; code is plaintext. | ai | |
| source-diff | obfuscated-file:esm2022/lib/harnesses/table-row.harness.mjs | AI (source-diff): Inline sourcemap only; code is plaintext. | ai | |
| source-diff | large-new-source-files | AI (source-diff): New harness files are legitimate Angular CDK test harnesses added as the library grows. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase explained by addition of ~40 new harness files, consistent with library expansion. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a well-known Angular/TypeScript implicit runtime dep; not a real phantom. | ai | |
| source-diff | obfuscated-file:esm2022/lib/harnesses/primeng/p-password.harness.mjs | AI (source-diff): Inline sourcemap only; code is plaintext. | ai | |
| source-diff | obfuscated-file:esm2022/lib/harnesses/div.harness.mjs | AI (source-diff): Same pattern: inline sourcemap comment, not obfuscation. | ai | |
| source-diff | obfuscated-file:esm2022/index.mjs | AI (source-diff): Re-export barrel with inline sourcemap; no obfuscation. | ai |
Versions (showing 51 of 79)
| Version | Deps | Published |
|---|---|---|
| 8.4.2 | 1 / 0 | |
| 8.4.1 | 1 / 0 | |
| 8.4.0 | 1 / 0 | |
| 8.3.1 | 1 / 0 | |
| 8.3.0 | 1 / 0 | |
| 8.2.2 | 1 / 0 | |
| 8.2.1 | 1 / 0 | |
| 8.2.0 | 1 / 0 | |
| 8.1.1 | 1 / 0 | |
| 8.1.0 | 1 / 0 | |
| 8.0.0 | 1 / 0 | |
| 7.9.2 | 1 / 0 | |
| 7.9.1 | 1 / 0 | |
| 7.9.0 | 1 / 0 | |
| 7.8.0 | 1 / 0 | |
| 7.7.2 | 1 / 0 | |
| 7.7.1 | 1 / 0 | |
| 7.7.0 | 1 / 0 | |
| 7.6.1 | 1 / 0 | |
| 7.6.0 | 1 / 0 | |
| 7.5.0 | 1 / 0 | |
| 7.4.0 | 1 / 0 | |
| 7.3.0 | 1 / 0 | |
| 7.2.0 | 1 / 0 | |
| 7.1.0 | 1 / 0 | |
| 7.0.6 | 1 / 0 | |
| 7.0.5 | 1 / 0 | |
| 7.0.4 | 1 / 0 | |
| 7.0.3 | 1 / 0 | |
| 7.0.2 | 1 / 0 | |
| 7.0.1 | 1 / 0 | |
| 7.0.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 |
v8.4.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.4.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.3.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.2.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.2.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.9.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.9.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.9.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.8.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.7.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.7.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.7.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.6.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.5.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.4.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-27. 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.
v7.3.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-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.
v7.2.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-10. 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.
v7.1.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-04. 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.
v7.0.6
2 findingsThis version was published by a different npm account than previous versions on 2026-02-04. 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.
v7.0.5
2 findingsThis version was published by a different npm account than previous versions on 2026-02-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.
v7.0.4
2 findingsThis version was published by a different npm account than previous versions on 2026-01-30. 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.
v7.0.3
2 findingsThis version was published by a different npm account than previous versions on 2026-01-30. 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.
v7.0.2
2 findingsThis version was published by a different npm account than previous versions on 2026-01-15. 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.
v7.0.1
2 findingsThis version was published by a different npm account than previous versions on 2026-01-15. 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.
v7.0.0
2 findingsThis version was published by a different npm account than previous versions on 2026-01-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.
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
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.21.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.20.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.19.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.18.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-27. 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.17.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-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.
v6.16.1
2 findingsThis version was published by a different npm account than previous versions on 2026-03-11. 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.16.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-10. 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.15.1
2 findingsThis version was published by a different npm account than previous versions on 2026-02-18. 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.15.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.
v6.14.4
2 findingsThis version was published by a different npm account than previous versions on 2026-02-04. 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.14.3
2 findingsThis version was published by a different npm account than previous versions on 2026-02-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.14.2
2 findingsThis version was published by a different npm account than previous versions on 2026-01-30. 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.14.1
2 findingsThis version was published by a different npm account than previous versions on 2026-01-30. 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.