@memberjunction/ng-testing
MemberJunction: Testing components and utilities for Angular applications
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:dist/lib/components/test-run-dialog.component.js | AI (source-diff): Angular ngc compiled output; long lines are template functions, not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:dist/lib/components/widgets/execution-context.component.js | AI (source-diff): Angular ngc compiled output; long lines are template functions, not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:dist/lib/components/test-feedback-dialog.component.js | AI (source-diff): Angular ngc compiled output; long lines are template functions, not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:dist/lib/components/widgets/test-results-matrix.component.js | AI (source-diff): Angular ngc compiled output; long lines are template functions, not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:dist/lib/components/widgets/evaluation-badge.component.js | AI (source-diff): Angular ngc compiled output; long lines are template functions, not malicious obfuscation. | ai | |
| phantom-deps | phantom-dep:rxjs | AI (phantom-deps): rxjs is a standard Angular peer dep; phantom detection is a false positive for Angular library packages. | ai | |
| phantom-deps | phantom-dep:@memberjunction/global | AI (phantom-deps): Same-org package; phantom detection unreliable for transitive/re-exported deps within a monorepo. | ai | |
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI publisher with SLSA attestation; consistent with org-wide automation adoption. | ai | |
| phantom-deps | phantom-dep:@memberjunction/ng-notifications | AI (phantom-deps): Same-org Angular library; stable false positive. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a known implicit Angular/TypeScript runtime dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@progress/kendo-angular-notification | AI (phantom-deps): Referenced in config files; Angular dep pattern, stable false positive. | ai | |
| phantom-deps | phantom-dep:@memberjunction/ng-shared | AI (phantom-deps): Same-org Angular library; phantom-dep heuristic unreliable for Angular module deps. | ai | |
| phantom-deps | phantom-dep:@progress/kendo-angular-grid | AI (phantom-deps): Referenced in config files; Angular peer/template dep pattern, not a real phantom. | ai | |
| phantom-deps | phantom-dep:@memberjunction/ng-base-types | AI (phantom-deps): Same-org Angular library; stable false positive. | ai | |
| phantom-deps | phantom-dep:@progress/kendo-angular-icons | AI (phantom-deps): Referenced in config files; Angular dep pattern, stable false positive. | ai | |
| phantom-deps | phantom-dep:@progress/kendo-theme-default | AI (phantom-deps): Referenced in config files (e.g. styles); stable false positive for Angular UI packages. | ai | |
| phantom-deps | phantom-dep:@memberjunction/ng-code-editor | AI (phantom-deps): Same-org Angular library; stable false positive. | ai | |
| phantom-deps | phantom-dep:@progress/kendo-angular-tooltip | AI (phantom-deps): Referenced in config files; Angular dep pattern, stable false positive. | ai |
Versions (showing 51 of 78)
| Version | Deps | Published |
|---|---|---|
| 5.39.0 | 13 / 3 | |
| 5.38.0 | 13 / 3 | |
| 5.37.0 | 13 / 3 | |
| 5.36.0 | 13 / 3 | |
| 5.35.0 | 13 / 3 | |
| 5.34.1 | 13 / 3 | |
| 5.34.0 | 13 / 3 | |
| 5.33.0 | 13 / 3 | |
| 5.32.0 | 13 / 3 | |
| 5.31.0 | 13 / 3 | |
| 5.30.1 | 13 / 3 | |
| 5.30.0 | 13 / 3 | |
| 5.29.0 | 13 / 3 | |
| 5.28.0 | 13 / 3 | |
| 5.27.1 | 13 / 3 | |
| 5.27.0 | 13 / 3 | |
| 5.26.0 | 13 / 3 | |
| 5.25.0 | 13 / 3 | |
| 5.24.0 | 13 / 3 | |
| 5.23.0 | 13 / 3 | |
| 5.22.0 | 12 / 3 | |
| 5.21.0 | 23 / 3 | |
| 5.20.0 | 23 / 3 | |
| 5.19.0 | 23 / 3 | |
| 5.18.0 | 23 / 3 | |
| 5.17.0 | 23 / 3 | |
| 5.16.0 | 23 / 3 | |
| 5.15.0 | 23 / 3 | |
| 5.14.0 | 23 / 3 | |
| 5.13.0 | 23 / 3 | |
| 5.12.0 | 23 / 3 | |
| 5.11.0 | 23 / 3 | |
| 5.10.1 | 23 / 3 | |
| 5.10.0 | 23 / 3 | |
| 5.9.0 | 23 / 3 | |
| 5.8.0 | 23 / 3 | |
| 5.7.0 | 23 / 3 | |
| 5.6.0 | 23 / 3 | |
| 5.5.0 | 23 / 3 | |
| 5.4.1 | 23 / 3 | |
| 5.4.0 | 23 / 3 | |
| 5.3.1 | 23 / 3 | |
| 5.3.0 | 23 / 3 | |
| 5.2.0 | 23 / 3 | |
| 5.1.0 | 23 / 3 | |
| 4.4.0 | 23 / 3 | |
| 4.3.1 | 23 / 3 | |
| 4.3.0 | 23 / 3 | |
| 4.2.0 | 23 / 2 | |
| 4.1.0 | 23 / 2 | |
| 3.4.0 | 23 / 2 |
v5.39.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.38.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.37.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.36.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.35.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.34.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.34.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.33.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.32.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.31.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.30.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.30.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.29.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.28.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.27.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.27.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.26.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.25.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.24.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.23.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.22.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.21.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.20.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.19.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.18.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.17.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.16.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.15.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.14.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.13.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.12.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.11.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.10.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.10.0
7 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.
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.9.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.8.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.7.0
7 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.
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.6.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.5.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.4.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.3.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.3.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.