@sap-ux/cds-odata-annotation-converter
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 org migrated publishing to GitHub Actions CI/CD with SLSA attestation; stable pattern for this package going forward. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): sap-ospo-admin is an SAP org admin account; consistent with the CI/CD migration. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by CI/CD migration is a known SAP open-ux-tools release pattern, not an account takeover indicator. | ai | |
| dependencies | unvetted-dep:@sap-ux/odata-vocabularies | AI (dependencies): Sibling SAP UX monorepo package; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@sap-ux/odata-annotation-core | AI (dependencies): Sibling SAP UX monorepo package; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@sap-ux/text-document-utils | AI (dependencies): Sibling SAP UX monorepo package; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@sap-ux/cds-annotation-parser | AI (dependencies): Sibling SAP UX monorepo package; stable false positive for this package family. | ai |
Versions (showing 45 of 45)
| Version | Deps | Published |
|---|---|---|
| 1.0.2 | 6 / 3 | |
| 1.0.1 | 6 / 3 | |
| 1.0.0 | 6 / 3 | |
| 0.8.1 | 6 / 3 | |
| 0.8.0 | 6 / 3 | |
| 0.7.17 | 6 / 3 | |
| 0.7.16 | 6 / 3 | |
| 0.7.15 | 6 / 3 | |
| 0.7.14 | 6 / 3 | |
| 0.7.13 | 6 / 3 | |
| 0.7.12 | 6 / 3 | |
| 0.7.11 | 6 / 3 | |
| 0.7.10 | 6 / 3 | |
| 0.7.9 | 6 / 3 | |
| 0.7.8 | 6 / 3 | |
| 0.7.7 | 6 / 3 | |
| 0.7.6 | 6 / 3 | |
| 0.7.5 | 6 / 3 | |
| 0.7.4 | 6 / 3 | |
| 0.7.3 | 6 / 3 | |
| 0.7.2 | 6 / 3 | |
| 0.7.1 | 6 / 3 | |
| 0.7.0 | 6 / 3 | |
| 0.6.19 | 6 / 3 | |
| 0.6.18 | 6 / 3 | |
| 0.6.17 | 6 / 3 | |
| 0.6.16 | 6 / 3 | |
| 0.6.15 | 6 / 3 | |
| 0.6.14 | 6 / 3 | |
| 0.6.13 | 6 / 3 | |
| 0.6.12 | 6 / 3 | |
| 0.6.11 | 6 / 3 | |
| 0.6.10 | 6 / 3 | |
| 0.6.9 | 6 / 3 | |
| 0.6.8 | 6 / 3 | |
| 0.6.7 | 6 / 3 | |
| 0.6.6 | 6 / 3 | |
| 0.6.5 | 6 / 3 | |
| 0.6.4 | 6 / 3 | |
| 0.6.3 | 6 / 3 | |
| 0.6.2 | 6 / 3 | |
| 0.6.1 | 6 / 3 | |
| 0.6.0 | 6 / 3 | |
| 0.5.9 | 6 / 3 | |
| 0.5.8 | 6 / 3 |
v1.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.1
2 findingsThis version was published by a different npm account than previous versions on 2026-05-20. 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.8.0
2 findingsThis version was published by a different npm account than previous versions on 2026-05-15. 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.7.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.16
2 findingsThis version was published by a different npm account than previous versions on 2026-03-30. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.15
2 findingsThis version was published by a different npm account than previous versions on 2026-03-26. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.14
2 findingsThis version was published by a different npm account than previous versions on 2026-03-17. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.13
2 findingsThis version was published by a different npm account than previous versions on 2026-03-16. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.12
2 findingsThis version was published by a different npm account than previous versions on 2026-03-11. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.11
2 findingsThis version was published by a different npm account than previous versions on 2026-03-10. This could indicate a legitimate maintainer transition or an account compromise.
Package 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. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.