← Home

@hasna/recordings

npm Repository Homepage

Speech-to-text recording tool with MCP and CLI — records, transcribes, and optionally enhances text using AI

10
Versions
Apache-2.0
License
Yes
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

andreihasna2

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:pg AI (phantom-deps): pg is used in the storage module which is bundled; not directly imported at the module level. ai
phantom-deps phantom-dep:zod AI (phantom-deps): zod used in config/type definitions; bundled output means no direct import visible to static analysis. ai
install-scripts install-script:postinstall AI (install-scripts): Postinstall only creates a local directory for audio recordings; no network calls or arbitrary code execution. ai

Versions (showing 10 of 10)

Version Deps Published
0.1.24 6 / 3
0.1.22 6 / 2
0.1.10 6 / 2
0.1.8 6 / 2
0.1.7 5 / 2
0.1.6 5 / 2
0.1.4 5 / 2
0.1.3 5 / 2
0.1.2 5 / 2
0.0.3 5 / 2

v0.1.24

1 finding
LOW No provenance attestation provenance

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

v0.1.22

1 finding
LOW No provenance attestation provenance

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

v0.1.10

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: mkdir -p $HOME/.hasna/recordings/audio 2>/dev/null || true

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