@sap-ux/control-property-editor
Control Property Editor
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 migrated to GitHub Actions CI publishing with SLSA attestation; stable pattern for this org. | ai | |
| source-diff | encoded-string-file:dist/app.js | AI (source-diff): Long strings are FluentUI/React bundle artifacts (ThemeGenerator palette code); stable false positive for this bundled app package. | ai |
Versions (showing 34 of 34)
| Version | Deps | Published |
|---|---|---|
| 1.0.9 | 0 / 39 | |
| 1.0.8 | 0 / 39 | |
| 1.0.7 | 0 / 39 | |
| 1.0.6 | 0 / 39 | |
| 1.0.5 | 0 / 39 | |
| 1.0.4 | 0 / 39 | |
| 1.0.3 | 0 / 39 | |
| 1.0.2 | 0 / 39 | |
| 1.0.1 | 0 / 39 | |
| 0.8.1 | 0 / 38 | |
| 0.8.0 | 0 / 38 | |
| 0.7.25 | 0 / 38 | |
| 0.7.24 | 0 / 38 | |
| 0.7.23 | 0 / 37 | |
| 0.7.22 | 0 / 37 | |
| 0.7.21 | 0 / 37 | |
| 0.7.20 | 0 / 38 | |
| 0.7.19 | 0 / 38 | |
| 0.7.18 | 0 / 38 | |
| 0.7.17 | 0 / 38 | |
| 0.7.16 | 0 / 38 | |
| 0.7.14 | 0 / 38 | |
| 0.7.13 | 0 / 38 | |
| 0.7.12 | 0 / 38 | |
| 0.7.11 | 0 / 38 | |
| 0.7.10 | 0 / 38 | |
| 0.7.9 | 0 / 38 | |
| 0.7.8 | 0 / 38 | |
| 0.7.7 | 0 / 38 | |
| 0.7.6 | 0 / 38 | |
| 0.7.5 | 0 / 38 | |
| 0.7.4 | 0 / 38 | |
| 0.7.3 | 0 / 38 | |
| 0.7.2 | 0 / 38 |
v1.0.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.22
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (devinea) than the most recent previously approved version (kranthie.sap) on 2026-03-17, but devinea is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.7.21
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (devinea) than the most recent previously approved version (kranthie.sap) on 2026-03-12, but devinea is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.7.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.