@stack-spot/portal-network
1. Create, at the root of your project, a file called `.env.local`. 2. Open the file and declare the following variable to replace the default urls: ```text VITE_NETWORK_OVERRIDES={"ai":"http://localhost:8080","agent-tools":"http://localhost:8082", "genAi
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Org-wide admin account transition, no behavioral change in diff. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Consistent with maintainer handoff, not takeover, given clean diff. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Routine API surface growth for this generated-client package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal @stack-spot scoped package; sparse metadata is expected for private org packages across all versions. | ai |
Versions (showing 51 of 242)
| Version | Deps | Published |
|---|---|---|
| 0.238.0 | 3 / 28 | |
| 0.237.0 | 3 / 28 | |
| 0.236.0 | 3 / 28 | |
| 0.235.3 | 3 / 28 | |
| 0.235.2 | 3 / 28 | |
| 0.235.1 | 3 / 28 | |
| 0.235.0 | 3 / 28 | |
| 0.234.1 | 3 / 28 | |
| 0.234.0 | 3 / 28 | |
| 0.233.0 | 3 / 28 | |
| 0.220.1 | 3 / 28 | |
| 0.194.2 | 3 / 27 | |
| 0.135.0 | 3 / 27 | |
| 0.134.1 | 3 / 27 | |
| 0.134.0 | 3 / 27 | |
| 0.133.3 | 3 / 27 | |
| 0.133.2 | 3 / 27 | |
| 0.133.1 | 3 / 27 | |
| 0.133.0 | 3 / 27 | |
| 0.132.0 | 3 / 27 | |
| 0.131.0 | 3 / 27 | |
| 0.130.0 | 3 / 27 | |
| 0.129.0 | 3 / 27 | |
| 0.128.1 | 3 / 27 | |
| 0.128.0 | 3 / 27 | |
| 0.127.1 | 3 / 27 | |
| 0.127.0 | 3 / 27 | |
| 0.126.0 | 3 / 27 | |
| 0.125.0 | 3 / 27 | |
| 0.124.2 | 3 / 27 | |
| 0.124.1 | 3 / 27 | |
| 0.124.0 | 3 / 27 | |
| 0.123.2 | 3 / 27 | |
| 0.123.1 | 3 / 27 | |
| 0.123.0 | 3 / 27 | |
| 0.122.1 | 3 / 27 | |
| 0.122.0 | 3 / 27 | |
| 0.121.1 | 3 / 27 | |
| 0.121.0 | 3 / 27 | |
| 0.120.0 | 3 / 27 | |
| 0.119.1 | 3 / 27 | |
| 0.119.0 | 3 / 27 | |
| 0.118.1 | 3 / 27 | |
| 0.118.0 | 3 / 27 | |
| 0.117.0 | 3 / 27 | |
| 0.116.4 | 3 / 27 | |
| 0.116.3 | 3 / 27 | |
| 0.116.2 | 3 / 27 | |
| 0.116.1 | 3 / 27 | |
| 0.116.0 | 3 / 27 | |
| 0.115.0 | 3 / 27 |
v0.238.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.237.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.220.1
2 findingsThis version was published by a different npm account than previous versions on 2026-02-12. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.194.2
2 findingsThis version was published by a different npm account than previous versions on 2025-10-31. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.117.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.116.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.116.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.116.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.116.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.116.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.115.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.