@sap-ux/preview-middleware
Preview middleware
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 | no-provenance | AI (provenance): Established package; provenance adoption is a forward-looking improvement, not a blocker. | ai | |
| provenance | publisher-changed | AI (provenance): SAP org migrated publishing to GitHub Actions CI with SLSA attestation; stable pattern for this package going forward. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): sap-ospo-admin is SAP's OSS admin account; consistent with org-level CI/CD transition. | ai | |
| dependencies | unvetted-dep:mem-fs-editor | AI (dependencies): Well-known Yeoman ecosystem utility; no malware indicators. | ai | |
| dependencies | unvetted-dep:@sap-ux/btp-utils | AI (dependencies): Same SAP org monorepo sibling; expected unvetted status. | ai | |
| dependencies | unvetted-dep:@sap-ux/adp-tooling | AI (dependencies): Same SAP org monorepo sibling; expected unvetted status. | ai | |
| dependencies | unvetted-dep:@sap-ux/feature-toggle | AI (dependencies): Same SAP org monorepo sibling; expected unvetted status. | ai | |
| dependencies | unvetted-dep:@sap-ux/control-property-editor-sources | AI (dependencies): Same SAP org monorepo sibling aliased via npm: protocol; expected unvetted status. | ai | |
| dependencies | unvetted-dep:@sap-ux/system-access | AI (dependencies): Same SAP org monorepo sibling; expected unvetted status. | ai | |
| dependencies | unvetted-dep:@sap-ux/i18n | AI (dependencies): Same SAP org monorepo sibling; expected unvetted status for co-released packages. | ai | |
| dependencies | unvetted-dep:@sap/bas-sdk | AI (dependencies): Official SAP BAS SDK; stable dependency for this package. | ai | |
| phantom-deps | phantom-dep:@sap-ux/system-access | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic fires on indirect usage patterns common in monorepos. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.26.11 | 13 / 20 | |
| 0.26.3 | 13 / 20 | |
| 0.25.32 | 13 / 20 | |
| 0.25.11 | 13 / 20 | |
| 0.23.95 | 13 / 20 | |
| 0.23.59 | 13 / 20 | |
| 0.23.50 | 13 / 20 | |
| 0.23.47 | 13 / 20 | |
| 0.23.21 | 13 / 20 | |
| 0.23.18 | 13 / 20 | |
| 0.23.12 | 13 / 20 | |
| 0.20.8 | 10 / 20 | |
| 0.20.2 | 10 / 20 |
v0.26.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.26.3
2 findingsThis version was published by a different npm account than previous versions on 2026-05-18. 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.
v0.25.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.95
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.