← Home

@stackone/ai

npm Repository Homepage

Tools for agents to perform actions on your SaaS

17
Versions
Apache-2.0
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

s1guillaumejorge.stackonestackone-publisher

Keywords

agentsaiai sdkmcpmodel context protocolstackonetools

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:hapi AI (typosquat): Scoped package @stackone/ai; not a typosquat of hapi. Levenshtein match is spurious. ai
typosquat typosquat.levenshtein:pg AI (typosquat): Scoped package @stackone/ai; not a typosquat of pg. Levenshtein match is spurious. ai
typosquat typosquat.levenshtein:qs AI (typosquat): Scoped package @stackone/ai; not a typosquat of qs. Levenshtein match is spurious. ai
typosquat typosquat.levenshtein:joi AI (typosquat): Scoped package @stackone/ai; not a typosquat of joi. Levenshtein match is spurious. ai
typosquat typosquat.levenshtein:ajv AI (typosquat): Scoped package @stackone/ai; not a typosquat of ajv. Levenshtein match is spurious. ai

Versions (showing 17 of 17)

Version Deps Published
2.10.0 3 / 16
2.9.2 3 / 16
2.9.1 3 / 16
2.9.0 3 / 16
2.8.1 3 / 16
2.8.0 3 / 16
2.7.0 3 / 16
2.6.0 3 / 16
2.5.1 3 / 16
2.5.0 3 / 16
2.4.0 3 / 16
2.3.0 3 / 16
2.2.0 3 / 22
2.1.0 3 / 22
2.0.9 4 / 22
2.0.7 4 / 22
1.1.1 4 / 19

v2.10.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.9.2

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.