@apple/cktool.api.base
Advanced tools
This package is part of the CKTool JS JavaScript client library suite and includes operations and TypeScript types related to "base".
This package is part of the CKTool JS JavaScript client library suite and includes operations and TypeScript types related to "base".
Each operation has a corresponding function that
returns a CancellablePromise that resolves
if successful and rejects if the operation fails.
Don't use this package directly. Use @apple/cktool.database
instead. All symbols from this package can be imported from
@apple/cktool.database.
BasePromisesApiMixin
Don't use this mixin directly. Instead, use PromisesApi
from @apple/cktool.database.
The following methods are added by the mixin.
getContainers
Fetches containers for a team.getTeams
Fetches a list of teams the current user is in.AuthenticationRequiredErrorCKDatabaseTypeCKEnvironmentContainerContainersResponseContainersSortByFieldRequestErrorSortDirectionTeamTeamsResponseFAQs
Apple CKTool JS 'base' API
The npm package @apple/cktool.api.base receives a total of 120 weekly downloads. As such, @apple/cktool.api.base popularity was classified as not popular.
We found that @apple/cktool.api.base demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 9 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
/Security News
A mini Shai-Hulud campaign compromised Red Hat Cloud Services npm packages to steal developer and CI/CD secrets during installation.
Research
/Security News
The North Korean malware loader hides in a Packagist-listed package and its GitHub branch to fetch and execute remote code in a likely Contagious Interview-style lure.
Security News
The Rust project is moving toward formal rules on LLM use in contributions after months of internal debate over maintainer burden, code quality, and contributor experience.