← Home

@sap-ux/cds-odata-annotation-converter

npm Repository
75
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 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 75 of 75)

Version Deps Published
1.0.8 6 / 3
1.0.7 6 / 3
1.0.6 6 / 3
1.0.5 6 / 3
1.0.4 6 / 3
1.0.3 6 / 3
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
0.5.7 6 / 3
0.5.6 6 / 3
0.5.5 6 / 3
0.5.3 6 / 4
0.5.2 6 / 4
0.5.1 6 / 4
0.5.0 6 / 4
0.4.1 6 / 4
0.4.0 6 / 4
0.3.10 6 / 4
0.3.9 6 / 4
0.3.8 6 / 4
0.3.7 6 / 4
0.3.6 6 / 4
0.3.5 6 / 6
0.3.4 6 / 6
0.3.3 6 / 6
0.3.2 6 / 6
0.3.1 6 / 6
0.3.0 6 / 6
0.2.9 6 / 6
0.2.8 6 / 6
0.2.7 6 / 6
0.2.6 6 / 5

v1.0.8

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.

v1.0.7

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.

v1.0.6

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.

v1.0.5

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.

v1.0.4

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.5.7

1 finding
LOW No provenance attestation provenance

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

v0.5.6

1 finding
LOW No provenance attestation provenance

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

v0.5.5

1 finding
LOW No provenance attestation provenance

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

v0.5.3

1 finding
LOW No provenance attestation provenance

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

v0.5.2

1 finding
LOW No provenance attestation provenance

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

v0.5.1

1 finding
LOW No provenance attestation provenance

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

v0.5.0

1 finding
LOW No provenance attestation provenance

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

v0.4.1

1 finding
LOW No provenance attestation provenance

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

v0.4.0

1 finding
LOW No provenance attestation provenance

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

v0.3.10

1 finding
LOW No provenance attestation provenance

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

v0.3.9

1 finding
LOW No provenance attestation provenance

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

v0.3.8

1 finding
LOW No provenance attestation provenance

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

v0.3.7

1 finding
LOW No provenance attestation provenance

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

v0.3.6

1 finding
LOW No provenance attestation provenance

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

v0.3.5

1 finding
LOW No provenance attestation provenance

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

v0.3.4

1 finding
LOW No provenance attestation provenance

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

v0.3.3

1 finding
LOW No provenance attestation provenance

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

v0.3.2

1 finding
LOW No provenance attestation provenance

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

v0.3.1

1 finding
LOW No provenance attestation provenance

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

v0.3.0

1 finding
LOW No provenance attestation provenance

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

v0.2.9

1 finding
LOW No provenance attestation provenance

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

v0.2.8

1 finding
LOW No provenance attestation provenance

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

v0.2.7

1 finding
LOW No provenance attestation provenance

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

v0.2.6

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.