← Home

@sap-ux/yaml

16
Versions
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

tqueckkranthie.sapsap_extncrepossap-ospo-admindevinea

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): SAP migrated publishing to GitHub Actions CI/CD with SLSA provenance; stable pattern for this org. ai
maintainer-change maintainer-added AI (maintainer-change): sap-ospo-admin is SAP's OSS admin account; consistent with org-level governance. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy followed by CI/CD migration is a known pattern for SAP open-ux-tools; not indicative of takeover. ai

Versions (showing 16 of 16)

Version Deps Published
1.0.2 2 / 1
1.0.1 2 / 1
1.0.0 2 / 1
0.18.0 2 / 1
0.17.7 2 / 1
0.17.6 2 / 1
0.17.5 2 / 1
0.17.4 2 / 1
0.17.3 2 / 2
0.17.2 2 / 2
0.17.1 2 / 2
0.17.0 2 / 2
0.16.0 2 / 2
0.15.1 2 / 2
0.15.0 2 / 2
0.14.2 2 / 2

v1.0.2

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.16.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.15.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.15.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.14.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.