← Home

@freesail/gateway

npm Homepage

Freesail Gateway - bridges the AI Agent with frontend

18
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

shanmugamnpm

Keywords

a2uifreesailagent-driven uigenerative uiai agent

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@modelcontextprotocol/sdk AI (phantom-deps): MCP SDK used via config/runtime; stable FP for this package. ai
phantom-deps phantom-dep:ajv AI (phantom-deps): Gateway config-driven validation; ajv referenced in config files, not direct imports — stable FP for this package. ai
phantom-deps phantom-dep:zod AI (phantom-deps): Schema validation used via config; stable FP for this package. ai
phantom-deps phantom-dep:express AI (phantom-deps): Gateway server dep loaded at runtime via config; stable FP for this package. ai
phantom-deps phantom-dep:ajv-formats AI (phantom-deps): Companion to ajv, config-driven; stable FP for this package. ai
phantom-deps phantom-dep:@freesail/core AI (phantom-deps): Same-org sibling dep; stable FP for this package. ai
phantom-deps phantom-dep:@freesail/logger AI (phantom-deps): Same-org sibling dep; stable FP for this package. ai
phantom-deps phantom-dep:vite AI (phantom-deps): vite is a declared runtime dep used for bundling; phantom-dep heuristic fires because it's not directly imported in source. ai

Versions (showing 18 of 18)

Version Deps Published
0.9.2 8 / 3
0.9.1 8 / 3
0.9.0 8 / 3
0.8.9 8 / 3
0.8.8 8 / 3
0.8.7 8 / 3
0.8.6 8 / 3
0.8.5 8 / 3
0.8.4 8 / 3
0.8.3 8 / 3
0.8.2 8 / 3
0.8.1 8 / 3
0.7.2 8 / 3
0.7.1 8 / 3
0.7.0 8 / 3
0.4.6 8 / 3
0.4.5 8 / 3
0.4.3 8 / 3

v0.9.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.9

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.8.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.8.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.8.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.7.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.7.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.7.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.4.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.4.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.