@sharpee/plugin-state-machine
State machine plugin for Sharpee engine - declarative puzzle and narrative orchestration (ADR-119, ADR-120)
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/core | AI (phantom-deps): Same-org scoped dep; likely used indirectly via plugin interface or re-exports. | ai | |
| phantom-deps | phantom-dep:@sharpee/plugins | AI (phantom-deps): Same-org scoped dep; likely used indirectly via plugin interface or re-exports. | ai | |
| phantom-deps | phantom-dep:@sharpee/world-model | AI (phantom-deps): Same-org scoped dep; likely used indirectly via plugin interface or re-exports. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 0.9.113 | 3 / 0 | |
| 0.9.111 | 3 / 0 | |
| 0.9.110 | 3 / 0 | |
| 0.9.109 | 3 / 0 | |
| 0.9.107 | 3 / 0 | |
| 0.9.106 | 3 / 0 | |
| 0.9.105 | 3 / 0 | |
| 0.9.104 | 3 / 0 | |
| 0.9.103 | 3 / 0 | |
| 0.9.102 | 3 / 0 | |
| 0.9.100 | 3 / 0 | |
| 0.9.99 | 3 / 0 | |
| 0.9.98 | 3 / 0 | |
| 0.9.97 | 3 / 0 | |
| 0.9.96 | 3 / 0 | |
| 0.9.95 | 3 / 0 | |
| 0.9.93 | 3 / 0 | |
| 0.9.92 | 3 / 0 | |
| 0.9.91 | 3 / 0 | |
| 0.9.90 | 3 / 0 | |
| 0.9.89 | 3 / 0 | |
| 0.9.88 | 3 / 0 | |
| 0.9.87 | 0 / 0 | |
| 0.9.86 | 0 / 0 | |
| 0.9.84 | 3 / 0 |
v0.9.113
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.111
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.110
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.109
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.107
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.106
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.105
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.104
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.103
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.102
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.100
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.99
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.98
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.97
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.96
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.95
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.93
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.92
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.91
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.90
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.89
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.88
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.