@memberjunction/ng-flow-editor
MemberJunction: Generic visual flow editor component powered by Foblex Flow, with an agent-specific Flow Agent Editor
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
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/flow-palette.component.js | AI (source-diff): Angular ngc compiled output; long lines are template function bodies, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/lib/components/flow-editor.component.js | AI (source-diff): Angular ngc compiled output; long lines are template function bodies, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/lib/components/flow-node.component.js | AI (source-diff): Angular ngc compiled output; long lines are template function bodies, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/lib/agent-editor/agent-properties-panel.component.js | AI (source-diff): Angular ngc compiled output; long lines are template function bodies, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/lib/agent-editor/flow-agent-editor.component.js | AI (source-diff): Angular ngc compiled output; long lines are template function bodies, not obfuscation. | ai | |
| phantom-deps | phantom-dep:@memberjunction/global | AI (phantom-deps): Same org scope; likely a transitive/implicit dependency within the MemberJunction monorepo. | ai | |
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI with SLSA provenance attestation is a legitimate supply chain improvement for the MemberJunction org. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is a same-version MemberJunction monorepo sibling; consistent with internal refactoring pattern. | ai | |
| dependencies | unvetted-dep:@foblex/platform | AI (dependencies): Companion @foblex library; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@foblex/flow | AI (dependencies): Legitimate Angular flow-editor library; documented dependency of this package's core functionality. | ai | |
| dependencies | unvetted-dep:@foblex/2d | AI (dependencies): Companion @foblex library; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@foblex/utils | AI (dependencies): Companion @foblex library; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@foblex/mediator | AI (dependencies): Companion @foblex library; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@foblex/2d | AI (phantom-deps): Referenced in config files only; transitive peer dep of @foblex/flow, not a direct import. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a well-known implicit runtime dependency for TypeScript compiled output. | ai | |
| phantom-deps | phantom-dep:@foblex/platform | AI (phantom-deps): Config-file reference only; stable false positive for this Angular library package. | ai | |
| phantom-deps | phantom-dep:@foblex/mediator | AI (phantom-deps): Config-file reference only; stable false positive for this Angular library package. | ai | |
| phantom-deps | phantom-dep:@foblex/utils | AI (phantom-deps): Config-file reference only; stable false positive for this Angular library package. | ai |
Versions (showing 53 of 53)
| Version | Deps | Published |
|---|---|---|
| 5.39.0 | 13 / 4 | |
| 5.38.0 | 13 / 4 | |
| 5.37.0 | 13 / 4 | |
| 5.36.0 | 13 / 4 | |
| 5.35.0 | 13 / 4 | |
| 5.34.1 | 13 / 4 | |
| 5.34.0 | 13 / 4 | |
| 5.33.0 | 13 / 4 | |
| 5.32.0 | 13 / 4 | |
| 5.31.0 | 13 / 4 | |
| 5.30.1 | 12 / 4 | |
| 5.30.0 | 12 / 4 | |
| 5.29.0 | 12 / 4 | |
| 5.28.0 | 12 / 4 | |
| 5.27.1 | 12 / 4 | |
| 5.27.0 | 12 / 4 | |
| 5.26.0 | 12 / 4 | |
| 5.25.0 | 12 / 4 | |
| 5.24.0 | 12 / 4 | |
| 5.23.0 | 12 / 4 | |
| 5.22.0 | 12 / 4 | |
| 5.21.0 | 12 / 4 | |
| 5.20.0 | 12 / 4 | |
| 5.19.0 | 12 / 4 | |
| 5.18.0 | 12 / 4 | |
| 5.17.0 | 12 / 4 | |
| 5.16.0 | 12 / 4 | |
| 5.15.0 | 12 / 4 | |
| 5.14.0 | 12 / 4 | |
| 5.13.0 | 12 / 4 | |
| 5.12.0 | 12 / 4 | |
| 5.11.0 | 12 / 4 | |
| 5.10.1 | 12 / 4 | |
| 5.10.0 | 12 / 4 | |
| 5.9.0 | 12 / 4 | |
| 5.8.0 | 12 / 4 | |
| 5.7.0 | 12 / 4 | |
| 5.6.0 | 12 / 4 | |
| 5.5.0 | 12 / 4 | |
| 5.4.1 | 12 / 4 | |
| 5.4.0 | 12 / 4 | |
| 5.3.1 | 12 / 4 | |
| 5.3.0 | 12 / 4 | |
| 5.2.0 | 12 / 4 | |
| 5.1.0 | 12 / 4 | |
| 5.0.0 | 12 / 4 | |
| 4.4.0 | 12 / 4 | |
| 4.3.1 | 12 / 4 | |
| 4.3.0 | 12 / 4 | |
| 4.2.0 | 12 / 3 | |
| 4.1.0 | 12 / 3 | |
| 4.0.0 | 12 / 3 | |
| 0.0.1 | 0 / 0 |
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.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
1 findingPublished 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
1 findingPublished 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
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 2026-02-18. This could indicate a legitimate maintainer transition or an account compromise.
v5.0.0
6 findingsNewly 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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
7 findingsThis version was published by a different npm account than previous versions on 2026-02-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.
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.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.