@awell-health/awell-sdk
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): Org-scoped internal SDK; missing description is a cosmetic issue, not a malware signal for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established package from a known org publisher; lack of Sigstore provenance is common and not a risk indicator here. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 0.1.31 | 6 / 18 | |
| 0.1.30 | 6 / 18 | |
| 0.1.29 | 6 / 18 | |
| 0.1.28 | 6 / 18 | |
| 0.1.27 | 6 / 18 | |
| 0.1.26 | 6 / 18 | |
| 0.1.25 | 6 / 18 | |
| 0.1.24 | 6 / 18 | |
| 0.1.23 | 6 / 18 | |
| 0.1.22 | 6 / 18 | |
| 0.1.21 | 6 / 18 | |
| 0.1.20 | 5 / 17 | |
| 0.1.19 | 5 / 17 | |
| 0.1.18 | 5 / 17 | |
| 0.1.17 | 5 / 17 | |
| 0.1.16 | 5 / 17 | |
| 0.1.15 | 5 / 17 | |
| 0.1.14 | 5 / 17 | |
| 0.1.13 | 4 / 17 | |
| 0.1.12 | 4 / 17 | |
| 0.1.11 | 3 / 17 | |
| 0.1.10 | 3 / 17 | |
| 0.1.9 | 3 / 17 | |
| 0.1.8 | 3 / 17 | |
| 0.1.7 | 2 / 17 | |
| 0.1.6 | 2 / 17 | |
| 0.1.5 | 3 / 16 | |
| 0.1.4 | 3 / 16 | |
| 0.1.3 | 3 / 16 | |
| 0.1.2 | 3 / 16 | |
| 0.1.1 | 3 / 16 | |
| 0.1.0 | 3 / 16 |
v0.1.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.