← Home

@foxxytux/buddy-ai

npm Repository Homepage

Unified LLM API with automatic model discovery and provider configuration

20
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

foxxytux

Keywords

aillmopenaianthropicgeminibedrockunifiedapi

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:ajv AI (phantom-deps): Transitive dependency used through SDK packages and validation; false positive from TypeScript compilation. ai
phantom-deps phantom-dep:chalk AI (phantom-deps): Transitive dependency for CLI output; false positive from TypeScript compilation. ai
phantom-deps phantom-dep:undici AI (phantom-deps): Runtime dependency for HTTP; false positive from TypeScript compilation. ai
phantom-deps phantom-dep:ajv-formats AI (phantom-deps): Transitive dependency for schema validation; false positive from TypeScript compilation. ai
phantom-deps phantom-dep:@sinclair/typebox AI (phantom-deps): Declared and used for schema validation; false positive from TypeScript compilation. ai
phantom-deps phantom-dep:zod-to-json-schema AI (phantom-deps): Declared and used for schema conversion; false positive from TypeScript compilation. ai

Versions (showing 20 of 20)

Version Deps Published
4.1.28 14 / 3
4.1.27 14 / 3
4.1.26 13 / 3
4.1.25 13 / 3
4.1.18 13 / 3
4.1.16 13 / 3
4.1.15 13 / 3
4.1.14 13 / 3
4.1.11 13 / 3
4.1.10 13 / 3
4.1.9 13 / 3
4.1.8 13 / 3
4.1.7 13 / 3
4.1.6 13 / 3
4.1.5 13 / 3
4.1.4 13 / 3
4.1.3 13 / 3
4.1.2 13 / 3
4.0.4 13 / 3
0.67.3 13 / 3

v4.1.28

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.

v4.1.27

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.

v4.1.26

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.

v4.1.25

1 finding
LOW No provenance attestation provenance

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

v4.1.18

1 finding
LOW No provenance attestation provenance

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

v4.1.16

1 finding
LOW No provenance attestation provenance

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

v4.1.15

1 finding
LOW No provenance attestation provenance

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

v4.1.14

1 finding
LOW No provenance attestation provenance

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

v4.1.11

1 finding
LOW No provenance attestation provenance

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

v4.1.10

1 finding
LOW No provenance attestation provenance

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

v4.1.9

1 finding
LOW No provenance attestation provenance

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

v4.1.8

1 finding
LOW No provenance attestation provenance

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

v4.1.7

1 finding
LOW No provenance attestation provenance

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

v4.1.6

1 finding
LOW No provenance attestation provenance

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

v4.1.5

1 finding
LOW No provenance attestation provenance

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

v4.1.4

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.

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

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

v4.0.4

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