Admin UI

[nadilas]

Description of change

Pull-Request Checklist

• [ ] Code is up-to-date with the main branch
• [ ] pnpm lint passes with this change
• [ ] This pull request links relevant issues as Fixes #0000
• [ ] Documentation has been updated to reflect this change
• [ ] The new commits follow conventions outlined in the conventional commit spec

📦 Published PR as canary version: Canary Versions

:sparkles: Test out this PR locally via: ```bash npm install @dotinc/bouncer-admin@0.1.1-canary.15.d3b48de.0 npm install @dotinc/bouncer-client@0.3.2-canary.15.d3b48de.0 npm install @dotinc/bouncer-core@0.7.2-canary.15.d3b48de.0 npm install @dotinc/bouncer-ui@0.1.1-canary.15.d3b48de.0 # or yarn add @dotinc/bouncer-admin@0.1.1-canary.15.d3b48de.0 yarn add @dotinc/bouncer-client@0.3.2-canary.15.d3b48de.0 yarn add @dotinc/bouncer-core@0.7.2-canary.15.d3b48de.0 yarn add @dotinc/bouncer-ui@0.1.1-canary.15.d3b48de.0 ```

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated
bouncer	❌ Failed (Inspect)			Mar 4, 2023 at 8:28AM (UTC)
usher	❌ Failed (Inspect)			Mar 4, 2023 at 8:28AM (UTC)

[what-the-diff[bot]]

• Added a new api for subscriptions
• Updated the admin to use this new API and removed configClientApi as it was not used anywhere else in the codebase
• Changed openapi generation from using @zodios/openapi to just plain old OpenAPI 3 spec builder (https://github.com/dot-industries/bouncer-core)

[nadilas]

Current dependencies on/for this PR:

• main
  • PR #15 👈
  • PR #17
  • PR #16
  • PR #19

This comment was auto-generated by Graphite.

[socket-security[bot]]

Socket Security Pull Request Report

Dependency issues detected: If you merge this pull request, you will not be alerted to the instances of these issues again.

📜 Install scripts

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.

Package	Script field	Source
prisma@3.15.2 (added)	install	packages/db/package.json via zod-prisma@0.5.4
prisma@4.11.0 (added)	install	packages/db/package.json via @prisma/client@4.11.0
protobufjs@7.2.2 (added)	postinstall	packages/api/package.json via @grpc/grpc-js@1.8.11
@prisma/engines@3.15.1-1.461d6a05159055555eb7dfb337c9fb271cbd4d7e (added)	postinstall	packages/db/package.json via zod-prisma@0.5.4
prisma@3.15.2 (added)	preinstall	packages/db/package.json via zod-prisma@0.5.4
prisma@4.11.0 (added)	preinstall	packages/db/package.json via @prisma/client@4.11.0

Pull request report summary

Issue	Status
Install scripts	⚠️ 6 issues
Native code	✅ 0 issues
Bin script shell injection	✅ 0 issues
Unresolved require	✅ 0 issues
Invalid package.json	✅ 0 issues
HTTP dependency	✅ 0 issues
Git dependency	✅ 0 issues
Potential typo squat	✅ 0 issues
Known Malware	✅ 0 issues
Telemetry	✅ 0 issues
Protestware/Troll package	✅ 0 issues

Bot Commands

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of package-name@version specifiers. e.g. @SocketSecurity ignore foo@1.0.0 bar@* or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore prisma@3.15.2
• @SocketSecurity ignore prisma@4.11.0
• @SocketSecurity ignore protobufjs@7.2.2
• @SocketSecurity ignore @prisma/engines@3.15.1-1.461d6a05159055555eb7dfb337c9fb271cbd4d7e

Powered by socket.dev

[nadilas]

@SocketSecurity ignore bouncer@0.0.1 turbo@1.7.3 @swc/core@1.3.32