← Home

anthropic-ai

npm Repository Homepage

感谢[Anthropic](https://console.anthropic.com/docs/api)的免费api,提供的ai回答功能

10
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

simon_he

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
install-scripts install-script:preinstall AI (install-scripts): npx only-allow pnpm is a standard pnpm monorepo pattern to enforce package manager; benign developer tooling accidentally left in published package. ai
install-scripts install-script:postinstall AI (install-scripts): simple-git-hooks sets up git hooks for contributors; a well-known safe dev tool accidentally included in published scripts, not malicious. ai
source-diff obfuscated-file:dist/index.mjs AI (source-diff): Package uses tsup --minify in its build script; long-line dist files are expected minified output, not obfuscation. Stable false positive for this package. ai
phantom-deps phantom-dep:lazy-js-utils AI (phantom-deps): lazy-js-utils is a declared runtime dependency that is likely bundled into the dist output by tsup; not a phantom dep risk for this package. ai

Versions (showing 10 of 10)

Version Deps Published
0.0.10 0 / 15
0.0.9 0 / 15
0.0.8 0 / 15
0.0.7 0 / 15
0.0.6 1 / 15
0.0.5 1 / 15
0.0.4 1 / 15
0.0.3 1 / 15
0.0.2 1 / 15
0.0.1 1 / 15

v0.0.10

1 finding
LOW No provenance attestation provenance

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

v0.0.9

1 finding
LOW No provenance attestation provenance

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

v0.0.8

1 finding
LOW No provenance attestation provenance

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

v0.0.7

1 finding
LOW No provenance attestation provenance

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

v0.0.6

1 finding
LOW No provenance attestation provenance

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

v0.0.5

2 findings
HIGH New obfuscated file: dist/index.mjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v0.0.4

1 finding
LOW No provenance attestation provenance

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

v0.0.3

1 finding
LOW No provenance attestation provenance

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

v0.0.2

1 finding
LOW No provenance attestation provenance

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

v0.0.1

3 findings
HIGH Package has 'preinstall' script install-scripts

Script: npx only-allow pnpm

HIGH Package has 'postinstall' script install-scripts

Script: simple-git-hooks

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.