@sap-ux/annotation-converter
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@sap-ux/vocabularies-types | AI (dependencies): Same SAP UX monorepo sibling; stable false positive for this package family. | ai |
Versions (showing 39 of 39)
| Version | Deps | Published |
|---|---|---|
| 0.10.21 | 1 / 1 | |
| 0.10.20 | 1 / 1 | |
| 0.10.19 | 1 / 1 | |
| 0.10.18 | 1 / 1 | |
| 0.10.17 | 1 / 1 | |
| 0.10.16 | 1 / 1 | |
| 0.10.15 | 1 / 1 | |
| 0.10.14 | 1 / 1 | |
| 0.10.13 | 1 / 1 | |
| 0.10.12 | 1 / 1 | |
| 0.10.11 | 1 / 1 | |
| 0.10.10 | 1 / 1 | |
| 0.10.9 | 1 / 1 | |
| 0.10.8 | 1 / 1 | |
| 0.10.7 | 1 / 1 | |
| 0.10.6 | 1 / 1 | |
| 0.10.5 | 1 / 1 | |
| 0.10.4 | 1 / 1 | |
| 0.10.3 | 1 / 1 | |
| 0.10.2 | 1 / 1 | |
| 0.10.1 | 1 / 1 | |
| 0.10.0 | 1 / 1 | |
| 0.9.11 | 1 / 1 | |
| 0.9.10 | 1 / 1 | |
| 0.9.9 | 1 / 1 | |
| 0.9.8 | 1 / 1 | |
| 0.9.7 | 1 / 1 | |
| 0.9.6 | 1 / 1 | |
| 0.9.5 | 1 / 1 | |
| 0.9.4 | 1 / 1 | |
| 0.9.3 | 1 / 1 | |
| 0.9.2 | 1 / 1 | |
| 0.9.1 | 1 / 1 | |
| 0.9.0 | 1 / 1 | |
| 0.8.15 | 1 / 1 | |
| 0.8.14 | 1 / 1 | |
| 0.8.13 | 1 / 1 | |
| 0.8.12 | 1 / 1 | |
| 0.8.11 | 1 / 1 |
v0.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.