@sap-ux/fiori-docs-embeddings
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from individual SAP dev account to GitHub Actions CI/CD with SLSA attestation is expected for SAP OSS packages. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): sap-ospo-admin is SAP's open-source admin account; addition is consistent with SAP org governance. | ai |
Versions (showing 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 1.2.6 | 0 / 13 | |
| 1.2.5 | 0 / 12 | |
| 1.2.4 | 0 / 12 | |
| 1.2.3 | 0 / 12 | |
| 1.2.2 | 0 / 12 | |
| 1.2.1 | 0 / 12 | |
| 1.2.0 | 0 / 12 | |
| 1.1.1 | 0 / 12 | |
| 1.1.0 | 0 / 12 | |
| 1.0.1 | 0 / 13 | |
| 0.5.1 | 0 / 12 | |
| 0.5.0 | 0 / 12 | |
| 0.4.18 | 0 / 12 | |
| 0.4.17 | 0 / 12 | |
| 0.4.16 | 0 / 12 | |
| 0.4.15 | 0 / 12 | |
| 0.4.14 | 0 / 12 | |
| 0.4.13 | 0 / 12 | |
| 0.4.12 | 0 / 12 | |
| 0.4.11 | 0 / 12 | |
| 0.4.10 | 0 / 12 | |
| 0.4.9 | 0 / 12 | |
| 0.4.8 | 0 / 12 | |
| 0.4.7 | 0 / 12 | |
| 0.4.6 | 0 / 12 | |
| 0.4.5 | 0 / 12 | |
| 0.4.4 | 0 / 12 | |
| 0.4.3 | 0 / 12 | |
| 0.4.2 | 0 / 10 |
v1.2.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.