ali-oss 4.11.0
aliyun oss(object storage service) node client
ali-oss@4.11.0 was published on 2017-10-25. Its manifest declares 21 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=4.
All ali-oss versions · Permanent reference to 4.11.0 · Latest release
Package specifications
| Version | 4.11.0 |
|---|---|
| License declaration | MIT |
| Published | 2017-10-25T02:54:38.980Z |
| Node.js requirement | >=4 |
| Type declarations | Not declared |
| Runtime dependency count | 21 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | Not supplied |
| Published file count | Not supplied |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | lib/client.js |
| Side effects declaration | Not declared |
| Direct advisories | Unknown |
| Resolved graph dependencies | Unknown |
| Repository stars | 2043 |
| Repository forks | 571 |
Install ali-oss 4.11.0
npm install ali-oss@4.11.0 pnpm add ali-oss@4.11.0 yarn add ali-oss@4.11.0
Runtime dependencies
- co ^4.6.0
- mime ^1.3.4
- debug ^2.2.0
- bowser ^1.6.0
- urllib ^2.17.1
- xml2js ^0.4.16
- address ^1.0.0
- copy-to ^2.0.1
- destroy ^1.0.4
- utility ^1.8.0
- co-defer ^1.0.0
- platform ^1.3.1
- sdk-base ^2.0.1
- co-gather ^0.0.1
- get-ready ^1.0.0
- dateformat ^2.0.0
- is-type-of ^1.0.0
- humanize-ms ^1.2.0
- end-or-error ^1.0.1
- agentkeepalive ^2.1.1
- merge-descriptors ^1.0.1
Peer requirements
- None declared
Optional dependencies
- None declared
How to interpret the specifications
Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.
Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.
OpenSSF repository checks
Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.
| Code-Review | 9/10 — Found 25/26 approved changesets -- score normalized to 9 |
|---|---|
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| Security-Policy | 3/10 — security policy file detected |
| Dangerous-Workflow | 10/10 — no dangerous workflow patterns detected |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Token-Permissions | 0/10 — detected GitHub workflow tokens with excessive permissions |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Pinned-Dependencies | 0/10 — dependency not pinned by hash detected -- score normalized to 0 |
| License | 10/10 — license file detected |
| Fuzzing | 0/10 — project is not fuzzed |
| SAST | 10/10 — SAST tool detected |
Evidence and freshness
- https://registry.npmjs.org/ali-oss/4.11.0 — retrieved 2026-10-31T23:42:16.700Z
- https://api.deps.dev/v3/projects/github.com%2Fali-sdk%2Fali-oss — retrieved 2026-10-31T22:50:26.437Z