@meistrari/tela-sdk-js
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 |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Established scoped SDK package; missing description is a cosmetic issue, not a risk indicator here. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 2.17.0 | 5 / 17 | |
| 2.16.0 | 5 / 17 | |
| 2.15.0 | 5 / 17 | |
| 2.14.0 | 5 / 17 | |
| 2.13.2 | 5 / 17 | |
| 2.13.1 | 5 / 17 | |
| 2.13.0 | 5 / 17 | |
| 2.12.0 | 4 / 17 | |
| 2.11.0 | 4 / 17 | |
| 2.5.0 | 4 / 16 | |
| 2.4.3 | 4 / 15 | |
| 2.4.2 | 4 / 15 | |
| 2.4.1 | 4 / 15 | |
| 2.4.0 | 4 / 15 | |
| 2.3.2 | 4 / 15 | |
| 2.3.1 | 4 / 15 | |
| 2.3.0 | 4 / 15 | |
| 2.2.1 | 4 / 15 | |
| 2.2.0 | 4 / 15 | |
| 2.1.0 | 4 / 15 | |
| 2.0.0 | 4 / 14 |
v2.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.