@alicloud/polardb20170801
English | [简体中文](README-CN.md) 
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 |
|---|---|---|---|---|
| source-diff | large-new-source-files | AI (source-diff): Alibaba Cloud SDK packages routinely add large numbers of generated API client files across versions; stable pattern for this package family. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Alibaba Cloud auto-generated SDK packages consistently lack repo/keywords; not a spam indicator for this publisher family. | ai | |
| provenance | no-provenance | AI (provenance): Alibaba Cloud SDK packages do not use Sigstore provenance; stable false positive for this publisher. | ai |
Versions (showing 51 of 61)
| Version | Deps | Published |
|---|---|---|
| 7.9.0 | 2 / 5 | |
| 7.8.0 | 2 / 5 | |
| 7.7.0 | 2 / 5 | |
| 7.6.0 | 2 / 5 | |
| 7.5.0 | 2 / 5 | |
| 7.4.0 | 2 / 5 | |
| 7.3.0 | 2 / 5 | |
| 7.2.0 | 2 / 5 | |
| 7.1.0 | 2 / 5 | |
| 7.0.0 | 2 / 5 | |
| 6.21.1 | 2 / 5 | |
| 6.21.0 | 2 / 5 | |
| 6.20.0 | 2 / 5 | |
| 6.19.0 | 2 / 5 | |
| 6.18.1 | 2 / 5 | |
| 6.18.0 | 2 / 5 | |
| 6.17.0 | 2 / 5 | |
| 6.16.0 | 2 / 5 | |
| 6.15.0 | 2 / 5 | |
| 6.14.1 | 2 / 5 | |
| 6.14.0 | 2 / 5 | |
| 6.13.0 | 2 / 5 | |
| 6.12.2 | 2 / 5 | |
| 6.12.1 | 2 / 5 | |
| 6.12.0 | 2 / 5 | |
| 6.11.1 | 2 / 5 | |
| 6.11.0 | 2 / 5 | |
| 6.10.5 | 2 / 5 | |
| 6.10.4 | 2 / 5 | |
| 6.10.3 | 2 / 5 | |
| 6.10.2 | 2 / 5 | |
| 6.10.1 | 2 / 5 | |
| 6.10.0 | 2 / 5 | |
| 6.9.0 | 2 / 5 | |
| 6.8.0 | 2 / 5 | |
| 6.7.4 | 2 / 5 | |
| 6.7.3 | 2 / 5 | |
| 6.7.2 | 2 / 5 | |
| 6.7.1 | 2 / 5 | |
| 6.7.0 | 2 / 5 | |
| 6.6.6 | 2 / 5 | |
| 6.6.5 | 2 / 5 | |
| 6.6.4 | 2 / 5 | |
| 6.6.3 | 2 / 5 | |
| 6.6.2 | 2 / 5 | |
| 6.6.1 | 2 / 5 | |
| 6.6.0 | 2 / 5 | |
| 6.5.0 | 2 / 5 | |
| 6.4.1 | 2 / 5 | |
| 6.4.0 | 2 / 5 | |
| 6.3.0 | 2 / 5 |
v7.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.7.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.7.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.