Downloads:
1,687
Downloads of v 1.2.1:
22
Last Update:
01 Mar 2024
Published Date:
01 Mar 2024
Reviewed Date:
25 Apr 2024
Reviewer:
Package Maintainer(s):
Software Author(s):
- SurrealDB Ltd.
- Tobie Morgan Hitchcock
Tags:
surrealdb database rdbms sql nosql surrealql cli admin graph community- Software Specific:
- Software Site
- Software Source
- Software License
- Software Docs
- Software Issues
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
SurrealDB
(Waiting for Maintainer to take corrective action)
- 1
- 2
- 3
1.2.1 | Updated: 01 Mar 2024
- Software Specific:
- Software Site
- Software Source
- Software License
- Software Docs
- Software Issues
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Downloads:
1,687
Downloads of v 1.2.1:
22
Published:
01 Mar 2024
Reviewed:
25 Apr 2024
Reviewer:
Maintainer(s):
Software Author(s):
- SurrealDB Ltd.
- Tobie Morgan Hitchcock
SurrealDB 1.2.1
(Waiting for Maintainer to take corrective action)
- 1
- 2
- 3
Some Checks Have Failed or Are Not Yet Complete
Not All Tests Have Passed
This version is in moderation and has not yet been approved. This means it doesn't show up under normal search.
- Until approved, you should consider this package version unsafe - it could do very bad things to your system (it probably doesn't but you have been warned, that's why we have moderation).
- This package version can change wildly over the course of moderation until it is approved. If you install it and it later has changes to this version, you will be out of sync with any changes that have been made to the package. Until approved, you should consider that this package version doesn't even exist.
- You cannot install this package under normal scenarios. See How to install package version under moderation for more information.
- There are also no guarantees that it will be approved.
There are versions of this package awaiting moderation (possibly just this one). See the Version History section below.
SurrealDB is a powerful multi-model database, built for the cloud, and designed to improve the development process of traditional and modern applications. SurrealDB’s premise is that developers should be able to build secure, modern, collaborative applications without needing to build complicated backend APIs and database layers, and without being forced into using a single data model or cloud platform.
From: https://raw.githubusercontent.com/surrealdb/surrealdb/main/LICENSE
LICENSE
Business Source License 1.1
Parameters
Licensor: SurrealDB Ltd.
Licensed Work: SurrealDB 1.0
The Licensed Work is (c) 2022 SurrealDB Ltd.
Additional Use Grant: You may make use of the Licensed Work, provided that
you may not use the Licensed Work for a Database
Service.
A “Database Service” is a commercial offering that
allows third parties (other than your employees and
contractors) to access the functionality of the
Licensed Work by creating tables whose schemas are
controlled by such third parties.
Change Date: 2026-01-01
Change License: Apache License, Version 2.0
For information about alternative licensing arrangements for the Software,
please visit: https://surrealdb.com
Notice
The Business Source License (this document, or the “License”) is not an Open
Source license. However, the Licensed Work will eventually be made available
under an Open Source License, as stated in this License.
License text copyright (c) 2017 MariaDB Corporation Ab, All Rights Reserved.
“Business Source License” is a trademark of MariaDB Corporation Ab.
-----------------------------------------------------------------------------
Business Source License 1.1
Terms
The Licensor hereby grants you the right to copy, modify, create derivative
works, redistribute, and make non-production use of the Licensed Work. The
Licensor may make an Additional Use Grant, above, permitting limited
production use.
Effective on the Change Date, or the fourth anniversary of the first publicly
available distribution of a specific version of the Licensed Work under this
License, whichever comes first, the Licensor hereby grants you rights under
the terms of the Change License, and the rights granted in the paragraph
above terminate.
If your use of the Licensed Work does not comply with the requirements
currently in effect as described in this License, you must purchase a
commercial license from the Licensor, its affiliated entities, or authorized
resellers, or you must refrain from using the Licensed Work.
All copies of the original and modified Licensed Work, and derivative works
of the Licensed Work, are subject to this License. This License applies
separately for each version of the Licensed Work and the Change Date may vary
for each version of the Licensed Work released by Licensor.
You must conspicuously display this License on each original or modified copy
of the Licensed Work. If you receive the Licensed Work in original or
modified form from a third party, the terms and conditions set forth in this
License apply to your use of that work.
Any use of the Licensed Work in violation of this License will automatically
terminate your rights under this License for the current and all other
versions of the Licensed Work.
This License does not grant you any right in any trademark or logo of
Licensor or its affiliates (provided that you may use a trademark or logo of
Licensor as expressly required by this License).
TO THE EXTENT PERMITTED BY APPLICABLE LAW, THE LICENSED WORK IS PROVIDED ON
AN “AS IS” BASIS. LICENSOR HEREBY DISCLAIMS ALL WARRANTIES AND CONDITIONS,
EXPRESS OR IMPLIED, INCLUDING (WITHOUT LIMITATION) WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, AND
TITLE.
MariaDB hereby grants you permission to use this License’s text to license
your works, and to refer to it using the trademark “Business Source License”,
as long as you comply with the Covenants of Licensor below.
Covenants of Licensor
In consideration of the right to use this License’s text and the “Business
Source License” name and trademark, Licensor covenants to MariaDB, and to all
other recipients of the licensed work to be provided by Licensor:
1. To specify as the Change License the GPL Version 2.0 or any later version,
or a license that is compatible with GPL Version 2.0 or a later version,
where “compatible” means that software provided under the Change License can
be included in a program with software provided under GPL Version 2.0 or a
later version. Licensor may specify additional Change Licenses without
limitation.
2. To either: (a) specify an additional grant of rights to use that does not
impose any additional restriction on the right granted in this License, as
the Additional Use Grant; or (b) insert the text “None”.
3. To specify a Change Date.
4. Not to modify this License in any other way.
Stop-Process -Name surreal 2> $null
VERIFICATION
Verification is intended to assist the Chocolatey moderators and community in verifying that this package's contents are trustworthy.
The checksum of the package is computed using `checksum -t sha256 -f $bin`.
The checksum can be validated by executing said command on the binary downloaded and installed by the official installer form the [project website](https://surrealdb.com/install):
`iwr https://windows.surrealdb.com -useb | iex`
This package is published by SurrealDB and is maintaned officially, with automatic updates powered by GitHub Actions continuous delivery.
Installation is quick and simple, with a CLI tool that can run the database, and which also acts as an SQL command line, and import and export tool.
If you like what we are building, it would be awesome if you check us out and leave a star at [GitHub](https://github.com/surrealdb/surrealdb).
If you have any questions feel free to reach out to me Tobie <[email protected]>.
Thank you!
md5: 0D516FE1F8D068C7724C1CDCAE7D9C21 | sha1: 32D6F25179F03974909E40C965A1F8440D8819C7 | sha256: 7BC099AC9930E94F733B59DAC380E9ECD2EB3C400AAFF10348E59A94DB67E479 | sha512: 26C08D8F27572B319670E55EE2DCF6DE5228362451282506F7558CAC08DFDDE247B5655E719257615304AF0818EBC1C27F0BE13A408023790F30190DB3380ACE
$ErrorActionPreference = 'Stop';
$packageArgs = @{
packageName = $env:ChocolateyPackageName
softwareName = 'surrealdb*'
fileType = 'exe'
}
$uninstalled = $false
[array]$key = Get-UninstallRegistryKey -SoftwareName $packageArgs['softwareName']
if ($key.Count -eq 1) {
$key | % {
$packageArgs['file'] = "$($_.UninstallString)"
if ($packageArgs['fileType'] -eq 'MSI') {
$packageArgs['silentArgs'] = "$($_.PSChildName) $($packageArgs['silentArgs'])"
$packageArgs['file'] = ''
} else {
}
Uninstall-ChocolateyPackage @packageArgs
}
} elseif ($key.Count -eq 0) {
Write-Warning "$packageName has already been uninstalled by other means."
} elseif ($key.Count -gt 1) {
Write-Warning "$($key.Count) matches found!"
Write-Warning "To prevent accidental data loss, no programs will be uninstalled."
Write-Warning "Please alert package maintainer the following keys were matched:"
$key | % {Write-Warning "- $($_.DisplayName)"}
}
Log in or click on link to see number of positives.
- surreal.exe (7bc099ac9930) - ## / 72
- surreal.1.2.1.nupkg (8ed440ec244f) - ## / 66
In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).
Chocolatey Pro provides runtime protection from possible malware.
Add to Builder | Version | Downloads | Last Updated | Status |
---|---|---|---|---|
SurrealDB 1.2.1 | 22 | Friday, March 1, 2024 |
Waiting for Maintainer
|
|
surrealdb (Install) 1.0.0-beta9 | 606 | Wednesday, April 19, 2023 | Exempted | |
surrealdb (Install) 1.0.0-beta8 | 780 | Sunday, October 9, 2022 | Exempted | |
surrealdb (Install) 1.0.0-beta7 | 279 | Wednesday, September 14, 2022 | Exempted |
2024 © SurrealDB Ltd.
This package has no dependencies.
Ground Rules:
- This discussion is only about SurrealDB and the SurrealDB package. If you have feedback for Chocolatey, please contact the Google Group.
- This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
- The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
- Tell us what you love about the package or SurrealDB, or tell us what needs improvement.
- Share your experiences with the package, or extra configuration or gotchas that you've found.
- If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
surrealdb (maintainer) on 26 Feb 2024 22:35:03 +00:00:
User 'surrealdb' (maintainer) submitted package.
surrealdb (maintainer) on 26 Feb 2024 22:42:03 +00:00:
User 'surrealdb' (maintainer) submitted package.
chocolatey-ops (reviewer) on 26 Feb 2024 23:16:41 +00:00:
surreal has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.
Guidelines
Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.
Notes
Notes typically flag things for both you and the reviewer to go over. Sometimes this is the use of things that may or may not be necessary given the constraints of what you are trying to do and/or are harder for automation to flag for other reasons. Items found in Notes might be Requirements depending on the context. A package version can be approved without addressing Note comments.
chocolatey-ops (reviewer) on 26 Feb 2024 23:18:58 +00:00:
surreal has passed automated package testing (verification). The next step in the process is package scanning.
Please visit https://gist.github.com/choco-bot/9971809346f6a05a9eb530ae9b72a57b for details.
This is an FYI only. There is no action you need to take.
chocolatey-ops (reviewer) on 26 Feb 2024 23:32:55 +00:00:
surreal has been flagged as part of automated virus scanning.
Package virus scanning found that at least 1 file within, or downloaded by, the package has between 1 and 5 VirusTotal detections associated with it.
This is not enough detections to prevent the approval of this package version.
surrealdb (maintainer) on 27 Feb 2024 18:02:44 +00:00:
User 'surrealdb' (maintainer) submitted package.
chocolatey-ops (reviewer) on 27 Feb 2024 18:36:55 +00:00:
surreal has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.
Guidelines
Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.
Notes
Notes typically flag things for both you and the reviewer to go over. Sometimes this is the use of things that may or may not be necessary given the constraints of what you are trying to do and/or are harder for automation to flag for other reasons. Items found in Notes might be Requirements depending on the context. A package version can be approved without addressing Note comments.
chocolatey-ops (reviewer) on 27 Feb 2024 19:27:49 +00:00:
surreal has passed automated package testing (verification). The next step in the process is package scanning.
Please visit https://gist.github.com/choco-bot/70d2fc7bd93c1bab658fa71746886f5d for details.
This is an FYI only. There is no action you need to take.
chocolatey-ops (reviewer) on 27 Feb 2024 19:45:07 +00:00:
surreal has been flagged as part of automated virus scanning.
Package virus scanning found that at least 1 file within, or downloaded by, the package has between 1 and 5 VirusTotal detections associated with it.
This is not enough detections to prevent the approval of this package version.
surrealdb (maintainer) on 28 Feb 2024 18:03:43 +00:00:
User 'surrealdb' (maintainer) submitted package.
chocolatey-ops (reviewer) on 28 Feb 2024 18:36:20 +00:00:
surreal has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.
Guidelines
Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.
Notes
Notes typically flag things for both you and the reviewer to go over. Sometimes this is the use of things that may or may not be necessary given the constraints of what you are trying to do and/or are harder for automation to flag for other reasons. Items found in Notes might be Requirements depending on the context. A package version can be approved without addressing Note comments.
chocolatey-ops (reviewer) on 28 Feb 2024 18:45:29 +00:00:
surreal has passed automated package testing (verification). The next step in the process is package scanning.
Please visit https://gist.github.com/choco-bot/64e9a8789423e6ce16d22ac15f5ec4c2 for details.
This is an FYI only. There is no action you need to take.
chocolatey-ops (reviewer) on 28 Feb 2024 18:56:44 +00:00:
surreal has been flagged as part of automated virus scanning.
Package virus scanning found that at least 1 file within, or downloaded by, the package has between 1 and 5 VirusTotal detections associated with it.
This is not enough detections to prevent the approval of this package version.
surrealdb (maintainer) on 29 Feb 2024 18:02:20 +00:00:
User 'surrealdb' (maintainer) submitted package.
chocolatey-ops (reviewer) on 29 Feb 2024 18:33:28 +00:00:
surreal has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.
Guidelines
Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.
Notes
Notes typically flag things for both you and the reviewer to go over. Sometimes this is the use of things that may or may not be necessary given the constraints of what you are trying to do and/or are harder for automation to flag for other reasons. Items found in Notes might be Requirements depending on the context. A package version can be approved without addressing Note comments.
chocolatey-ops (reviewer) on 29 Feb 2024 19:36:58 +00:00:
surreal has passed automated package testing (verification). The next step in the process is package scanning.
Please visit https://gist.github.com/choco-bot/eb0a7b23d2cdfb758240f1c142312284 for details.
This is an FYI only. There is no action you need to take.
chocolatey-ops (reviewer) on 29 Feb 2024 22:39:33 +00:00:
surreal has been flagged as part of automated virus scanning.
Package virus scanning found that at least 1 file within, or downloaded by, the package has between 1 and 5 VirusTotal detections associated with it.
This is not enough detections to prevent the approval of this package version.
surrealdb (maintainer) on 01 Mar 2024 18:03:17 +00:00:
User 'surrealdb' (maintainer) submitted package.
chocolatey-ops (reviewer) on 01 Mar 2024 18:35:31 +00:00:
surreal has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.
Guidelines
Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.
Notes
Notes typically flag things for both you and the reviewer to go over. Sometimes this is the use of things that may or may not be necessary given the constraints of what you are trying to do and/or are harder for automation to flag for other reasons. Items found in Notes might be Requirements depending on the context. A package version can be approved without addressing Note comments.
chocolatey-ops (reviewer) on 01 Mar 2024 18:49:02 +00:00:
surreal has passed automated package testing (verification). The next step in the process is package scanning.
Please visit https://gist.github.com/choco-bot/fa98b4e273f94f4a8b9c6290c17489ec for details.
This is an FYI only. There is no action you need to take.
chocolatey-ops (reviewer) on 01 Mar 2024 18:51:07 +00:00:
surreal has been flagged as part of automated virus scanning.
Package virus scanning found that at least 1 file within, or downloaded by, the package has between 1 and 5 VirusTotal detections associated with it.
This is not enough detections to prevent the approval of this package version.
AdmiringWorm (reviewer) on 25 Apr 2024 09:21:58 +00:00:
A few things before we can approve this package.
Instal-BinFile
in the install script, an equivalent call toUninstall-BinFile
must be added in the uninstall script.VERIFICATION.txt
file, do include information about downloading a random PowerShell script to validate the binary. Instead, the information should be in a persistable state that can't be modified. In this case, the URLs that can be used to download the binary file(s) should be included, and the checksum each of these binary files should also be defined in this file.$packageArgs
in the install script is completely unused, please either remove it or make use of it.Finally I'll leave with the following. Due to how you have created the package, you can rely on automatic functionality of Chocolatey CLI. In this case, that means removing both the install and uninstall script. The only thing you are doing is creating a bin/shim file for the embedded executable, which is what CHocolatey CLI will do automatically when the file is embedded inside of the nupkg archive.