@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 |
|---|---|---|---|---|
| source-diff | large-new-source-files | AI (source-diff): New files are bundled client build output for the added sibling dep. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Sibling SAP monorepo package, aliased npm dep, expected addition. | ai | |
| 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:@sap-ux/adp-tooling | AI (dependencies): Same SAP org monorepo sibling; 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/control-property-editor-sources | AI (dependencies): Same SAP org monorepo sibling aliased via npm: protocol; 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/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 | |
| 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 | |
| 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 49 of 49)
| Version | Deps | Published |
|---|---|---|
| 1.0.44 | 13 / 21 | |
| 1.0.31 | 13 / 21 | |
| 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.23.11 | 13 / 20 | |
| 0.20.73 | 11 / 19 | |
| 0.20.8 | 10 / 20 | |
| 0.20.2 | 10 / 20 | |
| 0.19.8 | 10 / 20 | |
| 0.13.43 | 8 / 18 | |
| 0.7.0 | 4 / 12 | |
| 0.6.3 | 3 / 12 | |
| 0.6.2 | 3 / 12 | |
| 0.6.1 | 3 / 12 | |
| 0.6.0 | 3 / 12 | |
| 0.5.7 | 3 / 12 | |
| 0.5.6 | 3 / 12 | |
| 0.5.5 | 3 / 12 | |
| 0.5.4 | 3 / 12 | |
| 0.5.2 | 3 / 12 | |
| 0.5.1 | 3 / 12 | |
| 0.5.0 | 3 / 12 | |
| 0.4.5 | 3 / 12 | |
| 0.4.4 | 3 / 12 | |
| 0.4.3 | 3 / 9 | |
| 0.4.2 | 3 / 9 | |
| 0.4.1 | 3 / 9 | |
| 0.4.0 | 3 / 9 | |
| 0.3.9 | 3 / 9 | |
| 0.3.8 | 3 / 9 | |
| 0.3.7 | 3 / 9 | |
| 0.3.6 | 3 / 9 | |
| 0.3.5 | 3 / 9 | |
| 0.3.4 | 3 / 9 | |
| 0.3.3 | 3 / 9 | |
| 0.3.2 | 3 / 9 | |
| 0.3.1 | 3 / 9 | |
| 0.3.0 | 3 / 9 | |
| 0.2.0 | 3 / 9 | |
| 0.1.0 | 2 / 6 |
v1.0.44
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.31
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.23.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.73
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.43
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.