![Maven Central Adds Sigstore Signature Validation](https://cdn.sanity.io/images/cgdhsj6q/production/7da3bc8a946cfb5df15d7fcf49767faedc72b483-1024x1024.webp?w=400&fit=max&auto=format)
Security News
Maven Central Adds Sigstore Signature Validation
Maven Central now validates Sigstore signatures, making it easier for developers to verify the provenance of Java packages.
@aims-api/aims-node
Advanced tools
npm install @aims-api/aims-node
In order to use the lirbary you need to obtain an API key. You can get a demo key by contacting us at hello@aimsapi.com.
TypeScript
// pages/api/searchByText.ts
import { NextApiRequest, NextApiResponse } from 'next'
import { Client as AIMSClient } from '@aims-api/aims-node'
const handler = async (req: NextApiRequest, res: NextApiResponse) => {
if (req.method === 'POST') {
try {
const { text, filter } = req.body
const aims = new AIMSClient({
authorization: 'YOUR_API_KEY',
})
const response = await aims.endpoints.query.byText({ text, detailed: true, filter })
return res.status(200).send(response)
} catch (error) {
return res.status(error.status).json(error.json)
}
}
return res.status(400).json('Method not allowed')
}
export default handler
// pages/api/searchByText.js
import { Client as AIMSClient } from '@aims-api/aims-node'
const handler = async (req, res) => {
if (req.method === 'POST') {
try {
const { text, filter } = req.body
const aims = new AIMSClient({
authorization: 'YOUR_API_KEY',
})
const response = await aims.endpoints.query.byText({
text,
detailed: true,
filter,
})
return res.status(200).send(response)
} catch (error) {
return res.status(error.status).json(error.json)
}
}
return res.status(400).json('Method not allowed')
}
export default handler
It is common to make a proxy request from client app to the server in order to hide foreign URL.
When you create a client instance in your codebase, you can then easily access all the existing endpoints via IDE autocomplete, as well as the required and optional parameters.
Library uses Zod for response validation, therefore you can use the types that are provided in every endpoint file.
Example
import { type SearchResponse } from '@aims-api/aims-node/dist/endpoints/search'
The library provides a set of endpoints that can be found in src/client/index.ts file by the endpoints
property on line #95.
List of all API endpoints could be found in AIMS API Documentation under Endpoints section, AIMS queries.
Both network errors and response structure errors are handled within a library, so the response is always a valid JavaScript Object in the following structure:
// successful request
{
success: true
data: any
}
// failed request
{
success: false
error: AxiosError | ZodError
}
See LICENSE for more information.
FAQs
Node.js library for AIMS API
The npm package @aims-api/aims-node receives a total of 0 weekly downloads. As such, @aims-api/aims-node popularity was classified as not popular.
We found that @aims-api/aims-node demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 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.
Security News
Maven Central now validates Sigstore signatures, making it easier for developers to verify the provenance of Java packages.
Security News
CISOs are racing to adopt AI for cybersecurity, but hurdles in budgets and governance may leave some falling behind in the fight against cyber threats.
Research
Security News
Socket researchers uncovered a backdoored typosquat of BoltDB in the Go ecosystem, exploiting Go Module Proxy caching to persist undetected for years.