← Home

@bunny.net/cli

npm

Command-line interface for [bunny.net](https://bunny.net) — manage databases, apps (Magic Containers), Edge Scripts, and more from your terminal.

22
Versions
—
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

kevin_at_bunnyantho-bunnynotrabbogdan-at-bunny

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@bunny.net/database-shell AI (phantom-deps): Same-org monorepo workspace dep; bundled into binary output. ai
phantom-deps phantom-dep:ora AI (phantom-deps): Bundled CLI; deps consumed in compiled binary, not directly imported in source. ai
phantom-deps phantom-dep:zod AI (phantom-deps): Bundled CLI; deps consumed in compiled binary, not directly imported in source. ai
phantom-deps phantom-dep:chalk AI (phantom-deps): Bundled CLI; deps consumed in compiled binary, not directly imported in source. ai
phantom-deps phantom-dep:yargs AI (phantom-deps): Bundled CLI; deps consumed in compiled binary, not directly imported in source. ai
phantom-deps phantom-dep:prompts AI (phantom-deps): Bundled CLI; deps consumed in compiled binary, not directly imported in source. ai
phantom-deps phantom-dep:smol-toml AI (phantom-deps): Bundled CLI; deps consumed in compiled binary, not directly imported in source. ai
phantom-deps phantom-dep:cli-table3 AI (phantom-deps): Bundled CLI; deps consumed in compiled binary, not directly imported in source. ai
phantom-deps phantom-dep:jsonc-parser AI (phantom-deps): Bundled CLI; deps consumed in compiled binary, not directly imported in source. ai
phantom-deps phantom-dep:@bunny.net/api AI (phantom-deps): Same-org monorepo workspace dep; bundled into binary output. ai
phantom-deps phantom-dep:@libsql/client AI (phantom-deps): Bundled CLI; deps consumed in compiled binary, not directly imported in source. ai
phantom-deps phantom-dep:@bunny.net/app-config AI (phantom-deps): Same-org monorepo workspace dep; bundled into binary output. ai
typosquat typosquat.levenshtein:joi AI (typosquat): Scoped @bunny.net namespace; Levenshtein match to 'joi' is coincidental, not a typosquat. ai

Versions (showing 22 of 22)

Version Deps Published
0.5.2 0 / 15
0.5.1 0 / 15
0.5.0 0 / 15
0.4.2 0 / 15
0.4.1 0 / 15
0.4.0 0 / 15
0.3.0 0 / 15
0.2.8 0 / 15
0.2.7 0 / 15
0.2.6 0 / 15
0.2.5 0 / 15
0.2.4 0 / 14
0.2.2 0 / 14
0.2.1 0 / 14
0.2.0 0 / 14
0.1.6 0 / 14
0.1.5 0 / 14
0.1.4 0 / 14
0.1.3 0 / 14
0.1.2 0 / 14
0.1.1 12 / 2
0.1.0 12 / 2

v0.5.2

1 finding
LOW No provenance attestation provenance

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

v0.5.1

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

1 finding
LOW No provenance attestation provenance

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

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

1 finding
LOW No provenance attestation provenance

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

v0.2.6

1 finding
LOW No provenance attestation provenance

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

v0.2.5

1 finding
LOW No provenance attestation provenance

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

v0.2.4

1 finding
LOW No provenance attestation provenance

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

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

v0.1.0

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.