Use typed clients
Keep client configuration, request payloads, response contracts, and exported service surfaces visible to TypeScript.
AuraOne Open / Hosted API integration
Keep the API contract typed and the package evidence visible.
Use the AuraOne client from TypeScript and Node.js while keeping configuration, package exports, runtime compatibility, and npm provenance reviewable.
For application and platform engineers integrating hosted AuraOne workflows into services, tooling, and controlled browser clients.
- License
- MIT; verify the license file for the selected source and package.
- Data boundary
- The SDK sends explicit requests to the configured AuraOne API. Browser credentials must be scoped and protected by the host application.
- License
- MIT; verify the license file for the selected source and package.
- Runtime boundary
- The SDK sends explicit requests to the configured AuraOne API. Browser credentials must be scoped and protected by the host application.
Product surface
The job, runtime boundary, and resulting artifact stay visible.
Inspect locally
Start from the source, then follow the reviewed README.
npm serves the verified 0.2.0 package. Pin the exact version and inspect registry provenance when reproducibility matters.
npm install @auraone/sdkRespect runtime boundaries
Separate Node.js and browser credential handling, base URL configuration, bundling, and error behavior.
Verify the package
Inspect the packed file list, exports, type declarations, clean-project consumption, npm provenance, and source tag.
AuraOne TypeScript SDK evaluation path
Source inspection, runtime testing, and release verification are separate checkpoints.
01
Inspect exports
Review the public package surface, type declarations, runtime targets, license, and dependency boundary.
Source and package manifest
02
Configure the client
Provide credentials and base URL through the host application's explicit secret boundary.
Application configuration
03
Run a typed request
Exercise the intended service from a clean consumer project and inspect errors and response typing.
Clean-project integration result
04
Verify publication
Match npm metadata, provenance, tarball contents, package version, source tag, and changelog.
Verified npm and GitHub Release record
Evidence packet preview
AuraOne TypeScript SDK evidence packet
The current release is trusted only when the source, artifact, runtime, and support records agree.
- Identity
- @auraone/sdk package, source revision, version, and MIT licenseRepository and npm metadata
- Exports
- JavaScript entry points, type declarations, package exports, and runtime compatibilityPacked package inspection
- Boundary
- Credential storage, API base URL, Node.js and browser behavior, and request errorsIntegration contract
- Publication
- Tarball integrity, provenance, clean install, source tag, changelog, and trusted publisherRelease preflight and npm verification
Availability
Current release and install details.
Public source, packages, downloads, and product images are reported from their current release records.
AuraOne TypeScript SDK release decision
npm serves @auraone/sdk 0.2.0, the public repository main and v0.2.0 release contain the matching source, and the GitHub Release includes the npm tarball, SBOM, and checksums.
@auraone/sdk
npm / 0.2.0
npm serves 0.2.0 and the GitHub Release contains the matching npm tarball, CycloneDX SBOM, and SHA-256 checksums.
SHA-256 e98e3907f954a15781187e531473c12c00ca7b22619b44e00bdf4614eed463b1