@sharpee/transcript-tester
Transcript-based testing tool for Sharpee interactive fiction
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 |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): Resolves a hardcoded relative path to the package's own bundled output; not user-controlled input. | ai | |
| phantom-deps | phantom-dep:@sharpee/core | AI (phantom-deps): Same-org monorepo sibling; consumed via bundled sharpee.js rather than direct import. | ai | |
| phantom-deps | phantom-dep:@sharpee/engine | AI (phantom-deps): Same-org monorepo sibling; consumed via bundled sharpee.js rather than direct import. | ai | |
| phantom-deps | phantom-dep:@sharpee/stdlib | AI (phantom-deps): Same-org monorepo sibling; consumed via bundled sharpee.js rather than direct import. | ai | |
| phantom-deps | phantom-dep:@sharpee/lang-en-us | AI (phantom-deps): Same-org monorepo sibling; consumed via bundled sharpee.js rather than direct import. | ai | |
| phantom-deps | phantom-dep:@sharpee/world-model | AI (phantom-deps): Same-org monorepo sibling; consumed via bundled sharpee.js rather than direct import. | ai | |
| phantom-deps | phantom-dep:@sharpee/parser-en-us | AI (phantom-deps): Same-org monorepo sibling; consumed via bundled sharpee.js rather than direct import. | ai | |
| phantom-deps | phantom-dep:@sharpee/text-service | AI (phantom-deps): Same-org monorepo sibling; consumed via bundled sharpee.js rather than direct import. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 0.9.113 | 9 / 0 | |
| 0.9.111 | 9 / 0 | |
| 0.9.107 | 9 / 0 | |
| 0.9.106 | 9 / 0 | |
| 0.9.105 | 9 / 0 | |
| 0.9.104 | 9 / 0 | |
| 0.9.103 | 9 / 0 | |
| 0.9.102 | 9 / 0 | |
| 0.9.100 | 9 / 0 | |
| 0.9.99 | 9 / 0 | |
| 0.9.98 | 9 / 0 | |
| 0.9.97 | 9 / 0 | |
| 0.9.96 | 9 / 0 | |
| 0.9.95 | 9 / 0 | |
| 0.9.93 | 9 / 0 | |
| 0.9.92 | 9 / 0 | |
| 0.9.91 | 9 / 0 | |
| 0.9.90 | 9 / 0 | |
| 0.9.89 | 9 / 0 | |
| 0.9.88 | 9 / 0 | |
| 0.9.87 | 2 / 0 | |
| 0.9.86 | 2 / 0 | |
| 0.9.84 | 9 / 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.96
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.93
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.92
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.91
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.90
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.88
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.87
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.84
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.