← Home

@telorun/ai

npm Repository Homepage
12
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

pasi

Keywords

teloaillmopenaianthropicollama

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:hapi AI (typosquat): Scoped package @telorun/ai; short name 'ai' causes spurious Levenshtein matches, not a typosquat. ai
typosquat typosquat.levenshtein:pg AI (typosquat): Same as above; false positive from short suffix. ai
typosquat typosquat.levenshtein:qs AI (typosquat): Same as above; false positive from short suffix. ai
typosquat typosquat.levenshtein:joi AI (typosquat): Same as above; false positive from short suffix. ai
typosquat typosquat.levenshtein:ajv AI (typosquat): Same as above; false positive from short suffix. ai

Versions (showing 12 of 12)

Version Deps Published
1.1.1 1 / 2
1.1.0 1 / 2
1.0.0 0 / 2
0.5.0 0 / 3
0.4.0 0 / 3
0.3.1 0 / 3
0.3.0 0 / 2
0.2.1 0 / 2
0.2.0 0 / 2
0.1.3 1 / 2
0.1.2 1 / 2
0.1.1 1 / 2

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.

v1.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.3

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.

v0.1.2

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.

v0.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.