@hasna/sessions
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:openai | AI (phantom-deps): Declared dep for AI session integration; stable false positive. | ai | |
| phantom-deps | phantom-dep:better-sqlite3 | AI (phantom-deps): Declared dep for SQLite index; stable false positive. | ai | |
| install-scripts | install-script:postinstall | AI (install-scripts): Postinstall only creates a local directory; no network calls or arbitrary code execution. | ai | |
| phantom-deps | phantom-dep:ink | AI (phantom-deps): ink is a CLI UI framework; likely used transitively or in config/build files for this Bun-built CLI package. | ai | |
| phantom-deps | phantom-dep:chalk | AI (phantom-deps): chalk is a common utility; referenced in config/build context, stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@inkjs/ui | AI (phantom-deps): UI component library for ink-based CLI; likely used in bundled output, stable false positive. | ai |
Versions (showing 57 of 57)
| Version | Deps | Published |
|---|---|---|
| 0.11.21 | 9 / 2 | |
| 0.11.20 | 9 / 2 | |
| 0.11.14 | 10 / 3 | |
| 0.11.10 | 10 / 3 | |
| 0.11.9 | 10 / 3 | |
| 0.11.8 | 9 / 3 | |
| 0.11.6 | 9 / 3 | |
| 0.11.5 | 9 / 3 | |
| 0.11.4 | 9 / 3 | |
| 0.11.3 | 9 / 3 | |
| 0.11.2 | 8 / 3 | |
| 0.11.1 | 8 / 3 | |
| 0.10.6 | 8 / 3 | |
| 0.10.5 | 8 / 3 | |
| 0.10.4 | 8 / 3 | |
| 0.10.3 | 8 / 3 | |
| 0.10.2 | 8 / 3 | |
| 0.10.1 | 8 / 3 | |
| 0.10.0 | 8 / 3 | |
| 0.9.2 | 8 / 3 | |
| 0.9.1 | 8 / 3 | |
| 0.9.0 | 8 / 3 | |
| 0.8.4 | 8 / 3 | |
| 0.8.3 | 8 / 3 | |
| 0.8.2 | 8 / 3 | |
| 0.8.1 | 8 / 3 | |
| 0.8.0 | 8 / 3 | |
| 0.7.2 | 8 / 3 | |
| 0.7.1 | 8 / 3 | |
| 0.7.0 | 8 / 3 | |
| 0.6.5 | 8 / 3 | |
| 0.6.4 | 8 / 3 | |
| 0.6.3 | 8 / 3 | |
| 0.6.2 | 8 / 3 | |
| 0.6.1 | 8 / 3 | |
| 0.6.0 | 8 / 3 | |
| 0.5.8 | 8 / 3 | |
| 0.5.7 | 8 / 3 | |
| 0.5.6 | 8 / 3 | |
| 0.5.5 | 8 / 3 | |
| 0.5.4 | 8 / 3 | |
| 0.5.3 | 8 / 3 | |
| 0.5.2 | 8 / 3 | |
| 0.5.1 | 8 / 3 | |
| 0.5.0 | 8 / 3 | |
| 0.4.0 | 8 / 3 | |
| 0.3.5 | 8 / 3 | |
| 0.3.4 | 8 / 3 | |
| 0.3.3 | 8 / 3 | |
| 0.3.2 | 8 / 3 | |
| 0.3.1 | 8 / 3 | |
| 0.3.0 | 8 / 3 | |
| 0.2.3 | 8 / 3 | |
| 0.2.2 | 8 / 3 | |
| 0.2.1 | 8 / 3 | |
| 0.2.0 | 8 / 3 | |
| 0.1.1 | 8 / 3 |
v0.11.21
2 findingsScript: mkdir -p $HOME/.hasna/sessions 2>/dev/null || true
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.20
2 findingsScript: mkdir -p $HOME/.hasna/sessions 2>/dev/null || true
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.14
2 findingsScript: mkdir -p $HOME/.hasna/sessions 2>/dev/null || true
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.