@sharpee/plugin-npc
NPC plugin for Sharpee engine - NPC behaviors and turn processing (ADR-070, ADR-120)
Supply chain provenance
Status for the latest visible version.
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): Monorepo plugin pattern; dependencies are re-exported or used indirectly via plugin interface. | ai | |
| phantom-deps | phantom-dep:@sharpee/stdlib | AI (phantom-deps): Monorepo plugin pattern; dependencies are re-exported or used indirectly via plugin interface. | ai | |
| phantom-deps | phantom-dep:@sharpee/plugins | AI (phantom-deps): Monorepo plugin pattern; dependencies are re-exported or used indirectly via plugin interface. | ai | |
| phantom-deps | phantom-dep:@sharpee/world-model | AI (phantom-deps): Monorepo plugin pattern; dependencies are re-exported or used indirectly via plugin interface. | ai |
Versions (showing 41 of 41)
| Version | Deps | Published |
|---|---|---|
| 4.1.2 | 4 / 0 | |
| 4.1.1 | 4 / 0 | |
| 4.1.0 | 4 / 0 | |
| 4.0.0 | 4 / 0 | |
| 3.6.0 | 4 / 0 | |
| 3.5.0 | 4 / 0 | |
| 3.3.0 | 4 / 0 | |
| 3.1.0 | 4 / 0 | |
| 3.0.0 | 4 / 0 | |
| 2.2.0 | 4 / 0 | |
| 2.1.1 | 4 / 0 | |
| 2.1.0 | 4 / 0 | |
| 2.0.0 | 4 / 0 | |
| 1.5.0 | 4 / 0 | |
| 1.1.1 | 4 / 0 | |
| 1.1.0 | 4 / 0 | |
| 1.0.8 | 4 / 0 | |
| 1.0.0 | 4 / 0 | |
| 0.9.113 | 4 / 0 | |
| 0.9.111 | 4 / 0 | |
| 0.9.107 | 4 / 0 | |
| 0.9.106 | 4 / 0 | |
| 0.9.105 | 4 / 0 | |
| 0.9.104 | 4 / 0 | |
| 0.9.103 | 4 / 0 | |
| 0.9.102 | 4 / 0 | |
| 0.9.100 | 4 / 0 | |
| 0.9.99 | 4 / 0 | |
| 0.9.98 | 4 / 0 | |
| 0.9.97 | 4 / 0 | |
| 0.9.96 | 4 / 0 | |
| 0.9.95 | 4 / 0 | |
| 0.9.93 | 4 / 0 | |
| 0.9.92 | 4 / 0 | |
| 0.9.91 | 4 / 0 | |
| 0.9.90 | 4 / 0 | |
| 0.9.89 | 4 / 0 | |
| 0.9.88 | 4 / 0 | |
| 0.9.87 | 0 / 0 | |
| 0.9.86 | 0 / 0 | |
| 0.9.84 | 4 / 0 |
v4.1.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.0
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (chicagodave) on 2026-07-26, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v3.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.