@sap-ux/axios-extension
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): SAP open-ux-tools migrated to GitHub Actions CI publishing with SLSA attestation; this is the expected new publisher for this package. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): sap-ospo-admin is SAP's org-level admin account; addition is consistent with SAP's CI/CD transition, not a takeover. | ai | |
| phantom-deps | phantom-dep:@sap-ux/feature-toggle | AI (phantom-deps): Declared runtime dep in same SAP org scope; phantom-dep heuristic is unreliable here. | ai |
Versions (showing 19 of 119)
| Version | Deps | Published |
|---|---|---|
| 1.16.1 | 10 / 4 | |
| 1.16.0 | 10 / 4 | |
| 1.15.1 | 10 / 4 | |
| 1.14.4 | 10 / 4 | |
| 1.14.3 | 10 / 4 | |
| 1.14.2 | 10 / 4 | |
| 1.14.1 | 10 / 4 | |
| 1.14.0 | 10 / 4 | |
| 1.13.1 | 10 / 4 | |
| 1.13.0 | 10 / 4 | |
| 1.12.6 | 10 / 4 | |
| 1.12.5 | 10 / 4 | |
| 1.12.4 | 10 / 4 | |
| 1.12.3 | 10 / 4 | |
| 1.12.2 | 10 / 4 | |
| 1.12.1 | 10 / 4 | |
| 1.12.0 | 10 / 4 | |
| 1.11.9 | 10 / 4 | |
| 1.11.8 | 10 / 4 |
v1.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.