← Home

@hasna/secrets

npm Repository Homepage
22
Versions
—
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

andreihasna2

Keywords

secretsvaultcredentialsagentsaicli

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff large-new-source-files AI (source-diff): New sdk:generate build step adds generated files, not injected code. ai
publish-pattern new-deps-added AI (publish-pattern): First-party @hasna/contracts dep, same org as package. ai
provenance missing-githead AI (provenance): Minor CI metadata gap, no behavioral change; publisher has strong track record. ai
phantom-deps phantom-dep:commander AI (phantom-deps): CLI dependency likely used indirectly through bin entrypoint. ai
phantom-deps phantom-dep:@hasna/events AI (phantom-deps): Same-org package, likely used indirectly. ai
phantom-deps phantom-dep:@aws-sdk/credential-providers AI (phantom-deps): AWS secrets-manager backend dep; convention-loaded. ai
phantom-deps phantom-dep:pg AI (phantom-deps): Used for optional Postgres-backed secrets storage, likely dynamic import. ai
phantom-deps phantom-dep:@aws-sdk/client-secrets-manager AI (phantom-deps): Framework-scoped AWS SDK; loaded by convention per finding description. ai
phantom-deps phantom-dep:@modelcontextprotocol/sdk AI (phantom-deps): Referenced in config files per finding; framework-convention loading pattern. ai
phantom-deps phantom-dep:@hasna/cloud AI (phantom-deps): Same-org scoped package; likely loaded by convention in this CLI tool. ai
install-scripts install-script:postinstall AI (install-scripts): Postinstall only creates a local config directory; no network calls or arbitrary code execution. ai

Versions (showing 22 of 22)

Version Deps Published
0.1.33 7 / 3
0.1.32 6 / 3
0.1.31 7 / 3
0.1.30 5 / 3
0.1.29 5 / 3
0.1.28 5 / 1
0.1.26 5 / 1
0.1.25 3 / 3
0.1.23 3 / 1
0.1.21 3 / 1
0.1.15 3 / 1
0.1.12 3 / 1
0.1.9 3 / 1
0.1.8 2 / 1
0.1.7 2 / 1
0.1.6 2 / 1
0.1.5 2 / 1
0.1.4 2 / 1
0.1.3 2 / 1
0.1.2 2 / 1
0.1.1 2 / 1
0.1.0 2 / 1

v0.1.33

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: andreihasna2.

LOW No provenance attestation provenance

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

v0.1.32

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

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

LOW No provenance attestation provenance

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

v0.1.31

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

Script: mkdir -p $HOME/.hasna/secrets 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.30

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

Script: mkdir -p $HOME/.hasna/secrets 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.29

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

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

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: andreihasna2.

LOW No provenance attestation provenance

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

v0.1.28

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

Script: mkdir -p $HOME/.hasna/secrets 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.26

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

Script: mkdir -p $HOME/.hasna/secrets 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.25

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

Script: mkdir -p $HOME/.hasna/secrets 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.23

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

Script: mkdir -p $HOME/.hasna/secrets 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.21

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

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

LOW No provenance attestation provenance

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

v0.1.15

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

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

LOW No provenance attestation provenance

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

v0.1.12

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

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

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

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.