@uipath/apollo-core
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Package now published via GitHub Actions CI/CD with SLSA attestation from official UiPath org repo; automated publishing is expected going forward. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers are UiPath org members consistent with org-level team management; stable pattern for this package. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of aoltean16 alongside org team restructuring; no takeover indicators given SLSA attestation. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 5.10.0 | 0 / 11 | |
| 5.9.1 | 0 / 10 | |
| 5.9.0 | 0 / 10 | |
| 5.8.1 | 0 / 10 | |
| 5.8.0 | 0 / 10 | |
| 5.7.4 | 0 / 10 | |
| 5.7.3 | 0 / 10 | |
| 5.7.2 | 0 / 10 | |
| 5.7.1 | 0 / 10 | |
| 5.7.0 | 0 / 10 | |
| 5.6.2 | 0 / 10 |
v5.10.0
2 findingsThis version was published by a different npm account than previous versions on 2026-06-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.
v5.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.