← Home

@rip-lang/ai

npm Repository Homepage

Persistent multi-model AI consultation MCP — discuss, panel, fresh-review, content-hashed attachments, live model catalog

11
Versions
MIT
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

shreeve

Keywords

mcpaillmopenaianthropicclaudegptpanelreviewrip

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:hapi AI (typosquat): Scoped package @rip-lang/ai; Levenshtein match against 'hapi' is a false positive on the scoped name. ai
typosquat typosquat.levenshtein:pg AI (typosquat): Scoped package @rip-lang/ai; Levenshtein match against 'pg' is a false positive on the scoped name. ai
typosquat typosquat.levenshtein:qs AI (typosquat): Scoped package @rip-lang/ai; Levenshtein match against 'qs' is a false positive on the scoped name. ai
typosquat typosquat.levenshtein:joi AI (typosquat): Scoped package @rip-lang/ai; Levenshtein match against 'joi' is a false positive on the scoped name. ai
typosquat typosquat.levenshtein:ajv AI (typosquat): Scoped package @rip-lang/ai; Levenshtein match against 'ajv' is a false positive on the scoped name. ai
phantom-deps phantom-dep:rip-lang AI (phantom-deps): rip-lang is the runtime interpreter; .rip files are executed by it, so no direct JS import is expected. ai

Versions (showing 11 of 11)

Version Deps Published
1.0.1 1 / 0
0.1.10 1 / 0
0.1.9 1 / 0
0.1.8 1 / 0
0.1.7 1 / 0
0.1.6 1 / 0
0.1.5 1 / 0
0.1.4 1 / 0
0.1.3 1 / 0
0.1.2 1 / 0
0.1.1 1 / 0

v1.0.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.

v0.1.10

1 finding
LOW No provenance attestation provenance

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

v0.1.9

1 finding
LOW No provenance attestation provenance

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

v0.1.8

1 finding
LOW No provenance attestation provenance

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

v0.1.7

1 finding
LOW No provenance attestation provenance

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

v0.1.6

1 finding
LOW No provenance attestation provenance

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

v0.1.5

1 finding
LOW No provenance attestation provenance

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

v0.1.4

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. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.2

1 finding
LOW No provenance attestation provenance

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

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.