@blocklet/js-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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:aws-sdk | AI (typosquat): Scoped ArcBlock package; Levenshtein match to aws-sdk is coincidental, not a typosquat. | ai |
Versions (showing 36 of 36)
| Version | Deps | Published |
|---|---|---|
| 1.17.12 | 11 / 12 | |
| 1.17.10 | 11 / 12 | |
| 1.17.9 | 11 / 12 | |
| 1.17.7 | 13 / 12 | |
| 1.17.5 | 13 / 12 | |
| 1.17.3 | 13 / 12 | |
| 1.17.2 | 11 / 12 | |
| 1.17.1 | 11 / 12 | |
| 1.17.0 | 11 / 12 | |
| 1.16.53 | 11 / 13 | |
| 1.16.52 | 11 / 13 | |
| 1.16.51 | 11 / 13 | |
| 1.16.50 | 11 / 13 | |
| 1.16.49 | 11 / 13 | |
| 1.16.48 | 11 / 13 | |
| 1.16.47 | 11 / 13 | |
| 1.16.46 | 11 / 13 | |
| 1.16.45 | 11 / 13 | |
| 1.16.44 | 11 / 13 | |
| 1.16.43 | 11 / 13 | |
| 1.16.42 | 11 / 13 | |
| 1.16.41 | 11 / 13 | |
| 1.16.40 | 11 / 13 | |
| 1.16.39 | 11 / 13 | |
| 1.16.38 | 11 / 13 | |
| 1.16.37 | 11 / 13 | |
| 1.16.36 | 11 / 13 | |
| 1.16.35 | 11 / 13 | |
| 1.16.34 | 11 / 13 | |
| 1.16.33 | 7 / 3 | |
| 1.16.32 | 7 / 3 | |
| 1.16.31 | 6 / 1 | |
| 1.16.30 | 6 / 1 | |
| 1.16.29 | 5 / 1 | |
| 1.16.28 | 4 / 1 | |
| 1.16.27 | 4 / 1 |
v1.16.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.