@swimlane/ngx-ui
Component & Style Library for Angular by Swimlane.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:types/swimlane-ngx-ui.d.ts | AI (source-diff): Angular compiled .d.ts bundle; long lines are concatenated type declarations, not obfuscation. Stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a standard Angular/TypeScript runtime dependency; phantom-dep false positive for this package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 52.1.0 | 4 / 0 | |
| 52.0.0 | 4 / 0 | |
| 51.5.0 | 4 / 0 | |
| 51.4.0 | 4 / 0 | |
| 51.3.2 | 4 / 0 | |
| 51.3.1 | 4 / 0 | |
| 51.3.0 | 4 / 0 | |
| 51.2.1 | 4 / 0 | |
| 51.1.0 | 4 / 0 | |
| 51.0.0 | 4 / 0 |
v51.3.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (steveblue) than the most recent previously approved version (anurag-p) on 2026-03-12, but steveblue is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v51.3.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (anurag-p) than the most recent previously approved version (ashraygupta) on 2026-02-27, but anurag-p is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v51.2.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (ashraygupta) than the most recent previously approved version (markcoleman1) on 2026-01-19, but ashraygupta is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v51.1.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (markcoleman1) than the most recent previously approved version (steveblue) on 2025-12-11, but markcoleman1 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v51.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.