gigabuddy 0.0.1 → 0.2.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (7) hide show
  1. package/LICENSE +21 -0
  2. package/README.md +5 -3
  3. package/bin/cli.js +14424 -83
  4. package/index.js +14397 -64
  5. package/package.json +4 -3
  6. package/src/lib/commands.d.ts +8 -10
  7. package/src/lib/doctor.d.ts +47 -0
package/LICENSE ADDED
@@ -0,0 +1,21 @@
1
+ MIT License
2
+
3
+ Copyright (c) 2026 Gigabuddy
4
+
5
+ Permission is hereby granted, free of charge, to any person obtaining a copy
6
+ of this software and associated documentation files (the "Software"), to deal
7
+ in the Software without restriction, including without limitation the rights
8
+ to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9
+ copies of the Software, and to permit persons to whom the Software is
10
+ furnished to do so, subject to the following conditions:
11
+
12
+ The above copyright notice and this permission notice shall be included in all
13
+ copies or substantial portions of the Software.
14
+
15
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16
+ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17
+ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18
+ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19
+ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20
+ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21
+ SOFTWARE.
package/README.md CHANGED
@@ -26,9 +26,11 @@ separately, so a staging login never becomes your production one.
26
26
 
27
27
  ## What lands on disk
28
28
 
29
- `login` stores a **refresh token** in `~/.gigabuddy/credentials.json` (0600).
30
- Platform tokens are minted from it on demand and live an hour, so nothing
31
- long-lived and fully-authoritative sits on your filesystem.
29
+ `login` stores a **refresh token** in `~/.gigabuddy/user-credentials.json`
30
+ (0600). Platform tokens are minted from it on demand and live an hour. The
31
+ session behind it is deliberately narrow — it identifies you, lets you see what
32
+ you can reach, install from the Gigabuddy registry, and run agents you sponsor;
33
+ it is not your full account authority.
32
34
 
33
35
  `login --npm` adds two lines to `~/.npmrc` (0600), leaving everything else in
34
36
  that file exactly where it was: