apigraveyard 1.0.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.
- package/.github/ISSUE_TEMPLATE/bug_report.md +28 -0
- package/.github/ISSUE_TEMPLATE/feature_request.md +22 -0
- package/.github/ROADMAP_ISSUES.md +169 -0
- package/LICENSE +21 -0
- package/README.md +501 -0
- package/bin/apigraveyard.js +686 -0
- package/hooks/pre-commit +203 -0
- package/package.json +34 -0
- package/scripts/install-hooks.js +182 -0
- package/src/database.js +518 -0
- package/src/display.js +534 -0
- package/src/scanner.js +294 -0
- package/src/tester.js +578 -0
|
@@ -0,0 +1,28 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: Bug Report
|
|
3
|
+
about: Report a bug or issue
|
|
4
|
+
title: '[BUG] '
|
|
5
|
+
labels: bug
|
|
6
|
+
assignees: himanshumudigonda
|
|
7
|
+
---
|
|
8
|
+
|
|
9
|
+
## 🐛 Bug Description
|
|
10
|
+
A clear description of what the bug is.
|
|
11
|
+
|
|
12
|
+
## Steps to Reproduce
|
|
13
|
+
1. Run `apigraveyard ...`
|
|
14
|
+
2. See error
|
|
15
|
+
|
|
16
|
+
## Expected Behavior
|
|
17
|
+
What you expected to happen.
|
|
18
|
+
|
|
19
|
+
## Actual Behavior
|
|
20
|
+
What actually happened.
|
|
21
|
+
|
|
22
|
+
## Environment
|
|
23
|
+
- OS: [e.g., Windows 11, macOS 14, Ubuntu 22.04]
|
|
24
|
+
- Node.js version: [e.g., 20.10.0]
|
|
25
|
+
- APIgraveyard version: [e.g., 1.0.0]
|
|
26
|
+
|
|
27
|
+
## Additional Context
|
|
28
|
+
Add any other context, screenshots, or error logs.
|
|
@@ -0,0 +1,22 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: Feature Request
|
|
3
|
+
about: Suggest an idea for APIgraveyard
|
|
4
|
+
title: '[FEATURE] '
|
|
5
|
+
labels: enhancement
|
|
6
|
+
assignees: himanshumudigonda
|
|
7
|
+
---
|
|
8
|
+
|
|
9
|
+
## 🚀 Feature Description
|
|
10
|
+
A clear description of the feature you'd like.
|
|
11
|
+
|
|
12
|
+
## Use Case
|
|
13
|
+
Why would this be useful? What problem does it solve?
|
|
14
|
+
|
|
15
|
+
## Proposed Solution
|
|
16
|
+
How do you think this should work?
|
|
17
|
+
|
|
18
|
+
## Alternatives Considered
|
|
19
|
+
Any alternative solutions you've considered.
|
|
20
|
+
|
|
21
|
+
## Additional Context
|
|
22
|
+
Any mockups, examples, or additional information.
|
|
@@ -0,0 +1,169 @@
|
|
|
1
|
+
# APIgraveyard Roadmap Issues
|
|
2
|
+
|
|
3
|
+
Copy and paste these into GitHub Issues at:
|
|
4
|
+
https://github.com/himanshumudigonda/apigraveyard/issues/new
|
|
5
|
+
|
|
6
|
+
---
|
|
7
|
+
|
|
8
|
+
## Issue 1: Support for More API Services
|
|
9
|
+
|
|
10
|
+
**Title:** [FEATURE] Add support for more API services
|
|
11
|
+
|
|
12
|
+
**Labels:** enhancement, help wanted
|
|
13
|
+
|
|
14
|
+
**Body:**
|
|
15
|
+
```
|
|
16
|
+
## 🚀 Feature Description
|
|
17
|
+
Add detection and validation support for more API services.
|
|
18
|
+
|
|
19
|
+
## Services to Add
|
|
20
|
+
- [ ] Azure (various keys)
|
|
21
|
+
- [ ] DigitalOcean
|
|
22
|
+
- [ ] Twilio
|
|
23
|
+
- [ ] SendGrid
|
|
24
|
+
- [ ] Mailchimp
|
|
25
|
+
- [ ] Slack
|
|
26
|
+
- [ ] Discord
|
|
27
|
+
- [ ] Replicate
|
|
28
|
+
- [ ] Cohere
|
|
29
|
+
- [ ] Mistral AI
|
|
30
|
+
- [ ] Together AI
|
|
31
|
+
|
|
32
|
+
## Implementation
|
|
33
|
+
1. Add regex patterns to `src/scanner.js`
|
|
34
|
+
2. Add test functions to `src/tester.js`
|
|
35
|
+
3. Update README with new services
|
|
36
|
+
|
|
37
|
+
## Contribution Welcome!
|
|
38
|
+
Feel free to pick a service and submit a PR!
|
|
39
|
+
```
|
|
40
|
+
|
|
41
|
+
---
|
|
42
|
+
|
|
43
|
+
## Issue 2: Cloud Sync Feature
|
|
44
|
+
|
|
45
|
+
**Title:** [FEATURE] Optional encrypted cloud sync
|
|
46
|
+
|
|
47
|
+
**Labels:** enhancement, future
|
|
48
|
+
|
|
49
|
+
**Body:**
|
|
50
|
+
```
|
|
51
|
+
## 🚀 Feature Description
|
|
52
|
+
Add optional encrypted cloud backup for the database.
|
|
53
|
+
|
|
54
|
+
## Use Cases
|
|
55
|
+
- Sync between multiple machines
|
|
56
|
+
- Backup important key inventory
|
|
57
|
+
- Disaster recovery
|
|
58
|
+
|
|
59
|
+
## Requirements
|
|
60
|
+
- End-to-end encryption (keys never visible to server)
|
|
61
|
+
- Optional - local-only should remain default
|
|
62
|
+
- Simple auth (GitHub OAuth?)
|
|
63
|
+
|
|
64
|
+
## Security Considerations
|
|
65
|
+
- Use strong encryption (AES-256)
|
|
66
|
+
- Never store unencrypted keys
|
|
67
|
+
- Allow users to self-host
|
|
68
|
+
```
|
|
69
|
+
|
|
70
|
+
---
|
|
71
|
+
|
|
72
|
+
## Issue 3: Team Sharing
|
|
73
|
+
|
|
74
|
+
**Title:** [FEATURE] Team sharing capabilities
|
|
75
|
+
|
|
76
|
+
**Labels:** enhancement, future
|
|
77
|
+
|
|
78
|
+
**Body:**
|
|
79
|
+
```
|
|
80
|
+
## 🚀 Feature Description
|
|
81
|
+
Allow teams to share API key inventories securely.
|
|
82
|
+
|
|
83
|
+
## Use Cases
|
|
84
|
+
- Team leads can see all keys across team projects
|
|
85
|
+
- Shared inventory for organization
|
|
86
|
+
- Revoke access when team members leave
|
|
87
|
+
|
|
88
|
+
## Proposed Features
|
|
89
|
+
- Team workspaces
|
|
90
|
+
- Role-based access (admin, member, viewer)
|
|
91
|
+
- Audit logs
|
|
92
|
+
- Key rotation reminders
|
|
93
|
+
```
|
|
94
|
+
|
|
95
|
+
---
|
|
96
|
+
|
|
97
|
+
## Issue 4: VS Code Extension
|
|
98
|
+
|
|
99
|
+
**Title:** [FEATURE] VS Code Extension for real-time detection
|
|
100
|
+
|
|
101
|
+
**Labels:** enhancement, good first issue
|
|
102
|
+
|
|
103
|
+
**Body:**
|
|
104
|
+
```
|
|
105
|
+
## 🚀 Feature Description
|
|
106
|
+
Create a VS Code extension that detects API keys in real-time.
|
|
107
|
+
|
|
108
|
+
## Features
|
|
109
|
+
- Highlight exposed keys in editor
|
|
110
|
+
- Quick actions: move to .env, add to .gitignore
|
|
111
|
+
- Status bar showing key count
|
|
112
|
+
- Integration with main CLI database
|
|
113
|
+
|
|
114
|
+
## References
|
|
115
|
+
- VS Code Extension API
|
|
116
|
+
- Similar: GitLens, Error Lens
|
|
117
|
+
```
|
|
118
|
+
|
|
119
|
+
---
|
|
120
|
+
|
|
121
|
+
## Issue 5: Browser Extension
|
|
122
|
+
|
|
123
|
+
**Title:** [FEATURE] Browser extension to detect keys on GitHub/GitLab
|
|
124
|
+
|
|
125
|
+
**Labels:** enhancement, future
|
|
126
|
+
|
|
127
|
+
**Body:**
|
|
128
|
+
```
|
|
129
|
+
## 🚀 Feature Description
|
|
130
|
+
Browser extension to scan public repositories for exposed keys.
|
|
131
|
+
|
|
132
|
+
## Use Cases
|
|
133
|
+
- Check if your repos have exposed keys
|
|
134
|
+
- Alert when viewing code with exposed keys
|
|
135
|
+
- Quick link to affected lines
|
|
136
|
+
|
|
137
|
+
## Platforms
|
|
138
|
+
- [ ] Chrome
|
|
139
|
+
- [ ] Firefox
|
|
140
|
+
- [ ] Edge
|
|
141
|
+
```
|
|
142
|
+
|
|
143
|
+
---
|
|
144
|
+
|
|
145
|
+
## Issue 6: Key Expiry Alerts
|
|
146
|
+
|
|
147
|
+
**Title:** [FEATURE] Key expiry notifications
|
|
148
|
+
|
|
149
|
+
**Labels:** enhancement
|
|
150
|
+
|
|
151
|
+
**Body:**
|
|
152
|
+
```
|
|
153
|
+
## 🚀 Feature Description
|
|
154
|
+
Get notified before API keys expire.
|
|
155
|
+
|
|
156
|
+
## Features
|
|
157
|
+
- Track expiry dates for keys
|
|
158
|
+
- Email/desktop notifications
|
|
159
|
+
- Integration with calendar
|
|
160
|
+
- Configurable reminder periods (7 days, 30 days)
|
|
161
|
+
|
|
162
|
+
## Commands
|
|
163
|
+
- `apigraveyard remind` - show upcoming expirations
|
|
164
|
+
- `apigraveyard set-expiry <key> <date>` - manually set expiry
|
|
165
|
+
```
|
|
166
|
+
|
|
167
|
+
---
|
|
168
|
+
|
|
169
|
+
Copy each issue above to: https://github.com/himanshumudigonda/apigraveyard/issues/new
|
package/LICENSE
ADDED
|
@@ -0,0 +1,21 @@
|
|
|
1
|
+
MIT License
|
|
2
|
+
|
|
3
|
+
Copyright (c) 2026 Himanshu Mudigonda
|
|
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.
|