@jay-framework/gemini-agent-plugin
Gemini AI agent plugin for jay-stack — embedded chat agent with page automation and server action calling
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@jay-framework/logger | AI (phantom-deps): Same-org sibling dep; likely re-exported or used indirectly through framework internals. | ai | |
| phantom-deps | phantom-dep:@jay-framework/runtime-automation | AI (phantom-deps): Same-org sibling dep; likely used indirectly through framework internals. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 0.18.0 | 9 / 10 | |
| 0.17.4 | 9 / 10 | |
| 0.17.3 | 9 / 10 | |
| 0.17.2 | 9 / 10 | |
| 0.17.1 | 9 / 10 | |
| 0.17.0 | 9 / 10 | |
| 0.16.5 | 9 / 10 | |
| 0.16.4 | 9 / 10 | |
| 0.16.3 | 9 / 10 | |
| 0.16.2 | 9 / 10 | |
| 0.16.1 | 9 / 10 | |
| 0.16.0 | 9 / 10 | |
| 0.15.6 | 9 / 10 | |
| 0.15.5 | 9 / 10 | |
| 0.15.4 | 9 / 10 | |
| 0.15.3 | 9 / 10 | |
| 0.15.2 | 9 / 10 | |
| 0.15.1 | 9 / 10 | |
| 0.15.0 | 9 / 10 | |
| 0.14.0 | 9 / 10 | |
| 0.13.0 | 8 / 10 | |
| 0.12.0 | 8 / 10 |
v0.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.