@sharpee/sharpee
Sharpee - Interactive Fiction Engine for TypeScript
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:@sharpee/media | AI (phantom-deps): Same-org aggregator pattern; stable FP. | ai | |
| phantom-deps | phantom-dep:@sharpee/character | AI (phantom-deps): Same-org monorepo sibling; stable false positive. | ai | |
| phantom-deps | phantom-dep:@sharpee/stdlib | AI (phantom-deps): Same org-scope meta-package pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:@sharpee/plugins | AI (phantom-deps): Same org-scope meta-package pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:@sharpee/if-domain | AI (phantom-deps): Same org-scope meta-package pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:@sharpee/lang-en-us | AI (phantom-deps): Same org-scope meta-package pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:@sharpee/plugin-npc | AI (phantom-deps): Same org-scope meta-package pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:@sharpee/ext-testing | AI (phantom-deps): Same org-scope meta-package pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:@sharpee/if-services | AI (phantom-deps): Same org-scope meta-package pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:@sharpee/text-blocks | AI (phantom-deps): Same org-scope meta-package pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:@sharpee/core | AI (phantom-deps): Meta-package re-exports org-scoped deps; phantom-dep heuristic is a stable false positive here. | ai | |
| phantom-deps | phantom-dep:@sharpee/parser-en-us | AI (phantom-deps): Same org-scope meta-package pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:@sharpee/text-service | AI (phantom-deps): Same org-scope meta-package pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:@sharpee/event-processor | AI (phantom-deps): Same org-scope meta-package pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:@sharpee/platform-browser | AI (phantom-deps): Same org-scope meta-package pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:@sharpee/plugin-scheduler | AI (phantom-deps): Same org-scope meta-package pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:@sharpee/transcript-tester | AI (phantom-deps): Same org-scope meta-package pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:@sharpee/plugin-state-machine | AI (phantom-deps): Same org-scope meta-package pattern; stable false positive. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process used in CLI build tool (build-browser.js); expected for a build/bundling CLI utility. | ai | |
| phantom-deps | phantom-dep:@sharpee/world-model | AI (phantom-deps): Same org-scope meta-package pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:@sharpee/engine | AI (phantom-deps): Same org-scope meta-package pattern; stable false positive. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 0.9.113 | 21 / 0 | |
| 0.9.111 | 21 / 0 | |
| 0.9.107 | 20 / 0 | |
| 0.9.106 | 20 / 0 | |
| 0.9.105 | 19 / 0 | |
| 0.9.104 | 19 / 0 | |
| 0.9.103 | 19 / 0 | |
| 0.9.102 | 19 / 0 | |
| 0.9.100 | 19 / 0 | |
| 0.9.99 | 19 / 0 | |
| 0.9.98 | 19 / 0 | |
| 0.9.97 | 19 / 0 | |
| 0.9.95 | 19 / 0 | |
| 0.9.89 | 18 / 0 | |
| 0.9.86 | 1 / 0 | |
| 0.9.85 | 18 / 0 | |
| 0.9.84 | 18 / 0 |
v0.9.113
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.111
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.107
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.106
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.105
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.104
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.103
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.102
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.100
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.99
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.98
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.97
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.95
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.89
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.86
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.85
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.84
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.