Downloads:
5,080
Downloads of v 1.0.0:
55
Last Update:
22 Apr 2024
Published Date:
22 Apr 2024
Reviewed Date:
28 Mar 2024
Reviewer:
Package Maintainer(s):
Software Author(s):
- Pierre Peltier
Tags:
gnu exa foss cli terminal coreutils directory list folder rainbow- Software Specific:
- Software Site
- Software Source
- Software License
- Software Issues
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
LSDeluxe (Portable)
(Waiting for Maintainer to take corrective action)
- 1
- 2
- 3
1.0.0 | Updated: 22 Apr 2024
- Software Specific:
- Software Site
- Software Source
- Software License
- Software Issues
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Downloads:
5,080
Downloads of v 1.0.0:
55
Published:
22 Apr 2024
Reviewed:
28 Mar 2024
Reviewer:
Maintainer(s):
Software Author(s):
- Pierre Peltier
LSDeluxe (Portable) 1.0.0
(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.
LSDeluxe is a colorful ls based replacement written in Rust.
Package Parameters
/GNU
- Install GNU ABI flavored executable variant instead of native MSVC ABI.
Prerequisites
Install the patched fonts of powerline nerd-font and/or font-awesome. Have a look at the Nerd Font README for more installation instructions. Don't forget to setup your terminal in order to use the correct font.
See this issue comment for detailed instructions on how to configure iTerm2 font settings correctly.
Configurations
Required
Enable nerd fonts for your terminal, URxvt for example:
.Xresources
URxvt*font: xft:Hack Nerd Font:style=Regular:size=11
F.A.Q.
Default Colors
In the future the possibility to customize the colors might be implemented.
For now, the default colors are:
User/Group | Permissions | File Types | Last time Modified | File Size |
---|---|---|---|---|
User | Read | Directory | within the last hour | Small File |
Group | Write | Executable File | within the last day | Medium File |
Execute | Non-Executable File | older | Large File | |
Execute with Stickybit | Broken Symlink | Non File | ||
No Access | Pipe/Symlink/Blockdevice/Socket/Special | |||
CharDevice |
Contributors
Everyone can contribute to this project, improving the code or adding functions. If anyone wants something to be added we will try to do it.
As this is being updated regularly, don't forget to rebase your fork before creating a pull-request.
Credits
Special thanks to:
- meain for all his contributions and reviews
- danieldulaney for the Windows integration
- sharkdp and his superb fd from which I have stolen a lot of CI stuff.
- athityakumar for the project colorls
- All the other contributors
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
VERIFICATION
Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.
Package can be verified like this:
1. Go to https://github.com/Peltoche/lsd, enter to releases and download from there.
x32: https://github.com/lsd-rs/lsd/releases/download/v1.0.0/lsd-v1.0.0-i686-pc-windows-msvc.zip
x64: https://github.com/lsd-rs/lsd/releases/download/v1.0.0/lsd-v1.0.0-x86_64-pc-windows-msvc.zip
x32-gnu: https://github.com/lsd-rs/lsd/releases/download/v1.0.0/lsd-v1.0.0-i686-pc-windows-gnu.zip
x64-gnu: https://github.com/lsd-rs/lsd/releases/download/v1.0.0/lsd-v1.0.0-x86_64-pc-windows-gnu.zip
to download the zip files. You may wish to rename one of the files.
2. You can use one of the following methods to obtain the SHA512 checksum:
- Use powershell function 'Get-FileHash'
- Use Chocolatey utility 'checksum.exe'
checksum: 16a5b8380fa9f8520f53b67366a184816c85cf7f1383acb353b33c3cffd1089b0be6ad64cf57194c0b5cc467458aa4eac3bc7c1026a95034f0bea26637b8bc37
checksum64: b877825006b98590d91d577ed8a46ddbffc355aed1735be3c80f8ca20f8857352fc0910f023f2498bfbd9ac90d53eb7ffb01687824a9bef4431438d798ad46ce
checksumgnu: 2508ad1516ceffc3d03d8daaa942d02e673aa49ca9ba97051b0b6568a37a69fc4b550a6f67579128342ffdd09fa0fffc72fe22f9b2a6b6d7cd11bd8575944bc7
checksumgnu64: 860d6a3e1d693d125571ea2612fff73b929f36229b2e6e5fb546d6af031a9b41f4e526450ffbe10325e9d6e3b1bc5d3a47abac0f43a2e692c2d49b3cad473433
File 'LICENSE.txt' obtained from:
https://github.com/Peltoche/lsd/blob/v1.0.0/LICENSE
md5: 1885DBFB972CE38594B01104B34B71D7 | sha1: E66C56BAB15C3202F3A12354F7A5603E338A228A | sha256: 253BA8F4EAC355220F1FA04ACEFE4748DB53B5462844457A3904BF36780C752D | sha512: 2508AD1516CEFFC3D03D8DAAA942D02E673AA49CA9BA97051B0B6568A37A69FC4B550A6F67579128342FFDD09FA0FFFC72FE22F9B2A6B6D7CD11BD8575944BC7
md5: 72B3E1E3C92ED6D76083F1D19D1E349B | sha1: D495BA34AC3B6B9554D11801E6B52FCC73537239 | sha256: 78B755A510F491885EAF79E114B9464F44E367475D17F7AED12A538DB36AB173 | sha512: 16A5B8380FA9F8520F53B67366A184816C85CF7F1383ACB353B33C3CFFD1089B0BE6AD64CF57194C0B5CC467458AA4EAC3BC7C1026A95034F0BEA26637B8BC37
md5: CD6E81C13C71C132FC850E5BE0ABBE3F | sha1: 7D353FA4E4E0F4BCD08B5747E28A6DAE498919F3 | sha256: AB286AE817428E0DA7D795321CD285DECC6BB1C6DA6711E9B6FD29F013F7F85E | sha512: 860D6A3E1D693D125571EA2612FFF73B929F36229B2E6E5FB546D6AF031A9B41F4E526450FFBE10325E9D6E3B1BC5D3A47ABAC0F43A2E692C2D49B3CAD473433
md5: 74DC04ED068C9BCFB2F3ECED035E7B19 | sha1: B9AE353F782CCAB81693EB2643DC68551A8E108E | sha256: 2E458DE6521E9D9B0A9B3D361BB77698158EFAEACAB43D3BB7AF7E03BB92DDB9 | sha512: B877825006B98590D91D577ED8A46DDBFFC355AED1735BE3C80F8CA20F8857352FC0910F023F2498BFBD9AC90D53EB7FFB01687824A9BEF4431438D798AD46CE
Log in or click on link to see number of positives.
- lsd.1.0.0.nupkg (52175321563b) - ## / 64
- lsd-v1.0.0-i686-pc-windows-gnu.zip (253ba8f4eac3) - ## / 65
- lsd-v1.0.0-i686-pc-windows-msvc.zip (78b755a510f4) - ## / 64
- lsd-v1.0.0-x86_64-pc-windows-gnu.zip (ab286ae81742) - ## / 63
- lsd-v1.0.0-x86_64-pc-windows-msvc.zip (2e458de6521e) - ## / 63
- lsd.exe (7d64741319d7) - ## / 72
- lsd.exe (7d0c71fe45d2) - ## / 71
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 |
---|---|---|---|---|
LSDeluxe (Portable) 1.1.2 | 308 | Thursday, March 28, 2024 | Approved | |
LSDeluxe (Portable) 1.1.1 | 37 | Wednesday, March 27, 2024 | Approved | |
LSDeluxe (Portable) 1.1.0 | 77 | Monday, March 25, 2024 | Approved | |
LSDeluxe (Portable) 1.0.0 | 55 | Monday, April 22, 2024 |
Waiting for Maintainer
|
|
LSDeluxe (Portable) 0.23.0 | 1851 | Saturday, October 8, 2022 | Approved | |
LSDeluxe (Portable) 0.22.0 | 563 | Tuesday, June 14, 2022 | Approved | |
LSDeluxe (Portable) 0.21.0 | 594 | Wednesday, January 19, 2022 | Approved | |
LSDeluxe (Portable) 0.20.1 | 858 | Monday, March 8, 2021 | Approved | |
LSDeluxe (Portable) 0.19.0 | 290 | Wednesday, December 16, 2020 | Approved | |
LSDeluxe (Portable) 0.18.0 | 185 | Friday, October 16, 2020 | Approved | |
LSDeluxe (Portable) 0.17.0 | 202 | Monday, September 21, 2020 | Approved |
Copyright © 2018 - 2023 Pierre Peltier
New Features
:sparkles: theme: bring icon theme to lsd by @zwpaper in https://github.com/lsd-rs/lsd/pull/707
Respect
hidden
flag on Windows by @Icxolu in https://github.com/lsd-rs/lsd/pull/766Theme colors for inode and links are now being applied to the output by @d-sonuga in https://github.com/lsd-rs/lsd/pull/768
Localization support by @scarf005 in https://github.com/lsd-rs/lsd/pull/820
Git integration by @hpwxf in https://github.com/lsd-rs/lsd/pull/822
Added complete color theming support for Git by @k4yt3x in https://github.com/lsd-rs/lsd/pull/852
Enhancements and Bug Fix
add quotes and escapes for necessary filenames by @merelymyself in https://github.com/lsd-rs/lsd/pull/746
fix: do not quote filename when piping to another program by @TeamTamoad in https://github.com/lsd-rs/lsd/pull/748
Fix showing every file as executable on Windows by @Icxolu in https://github.com/lsd-rs/lsd/pull/769
Fix Bug: Handle -L with broken symlink #457 by @r3dArch in https://github.com/lsd-rs/lsd/pull/754
Avoid using clap deprecated features by @sudame in https://github.com/lsd-rs/lsd/pull/787
Switch arg parsing to clap v4 with derive by @tranzystorek-io in https://github.com/lsd-rs/lsd/pull/818
Icon theme with overrides from config by @sudame in https://github.com/lsd-rs/lsd/pull/792
Move locale based date behind a flag by @meain in https://github.com/lsd-rs/lsd/pull/840
Fixed file size colorizing with
--size=bytes
argument by @bells307 in https://github.com/lsd-rs/lsd/pull/856Added new
custom
option for color config, marked themes folder as deprecated. by @peppidesu in https://github.com/lsd-rs/lsd/pull/851Add Version Sort by @juansc in https://github.com/lsd-rs/lsd/pull/843
Added newlines to warning message by @juansc in https://github.com/lsd-rs/lsd/pull/869
Icons
Add kotlin icon by @LeeWeeder in https://github.com/lsd-rs/lsd/pull/759
Implement most icons from #764 by @meain in https://github.com/lsd-rs/lsd/pull/779
Add icons for cjs, cts and mts by @nix6839 in https://github.com/lsd-rs/lsd/pull/829
Fix obsolete Nerd Font icons by @nix6839 in https://github.com/lsd-rs/lsd/pull/830
Update icon.rs to add zig extension icon by @CraigglesO in https://github.com/lsd-rs/lsd/pull/839
Make
tox.ini
files use the gear/settings icon by @alichtman in https://github.com/lsd-rs/lsd/pull/859Make
.profile
have the same icon asprofile
by @alichtman in https://github.com/lsd-rs/lsd/pull/850Update src/theme/icon.rs to add Svelte icon by @Marcos-Gamarra in https://github.com/lsd-rs/lsd/pull/871
Others
Fix symlink_arrow test intercepting cli args by @tranzystorek-io in https://github.com/lsd-rs/lsd/pull/744
chore: fix typo by @hezhizhen in https://github.com/lsd-rs/lsd/pull/753
Add note about not icon config not being in a release yet by @meain in https://github.com/lsd-rs/lsd/pull/772
Small typo in README by @meain in https://github.com/lsd-rs/lsd/pull/773
ci: :sparkles: add clap deprecated checks by @zwpaper in https://github.com/lsd-rs/lsd/pull/788
Add installation information for debian sid and bookworm by @alexanderkjall in https://github.com/lsd-rs/lsd/pull/790
Update README / Note snap discontinuation by @Semnodime in https://github.com/lsd-rs/lsd/pull/805
Drop size_value from blocks docs by @meain in https://github.com/lsd-rs/lsd/pull/806
Update docs about supported block options by @meain in https://github.com/lsd-rs/lsd/pull/808
:sparkles: chore: add new bug template by @zwpaper in https://github.com/lsd-rs/lsd/pull/833
Clarify that ubuntu 23.04 can use apt to install lsd by @alexanderkjall in https://github.com/lsd-rs/lsd/pull/842
:tada: add zwpaper to code owner by @zwpaper in https://github.com/lsd-rs/lsd/pull/860
Updated documentation to include SHELL_COMPLETIONS_DIR by @jhalloy in https://github.com/lsd-rs/lsd/pull/861
New Contributors
@merelymyself made their first contribution in https://github.com/lsd-rs/lsd/pull/746
@hezhizhen made their first contribution in https://github.com/lsd-rs/lsd/pull/753
@LeeWeeder made their first contribution in https://github.com/lsd-rs/lsd/pull/759
@Icxolu made their first contribution in https://github.com/lsd-rs/lsd/pull/766
@d-sonuga made their first contribution in https://github.com/lsd-rs/lsd/pull/768
@r3dArch made their first contribution in https://github.com/lsd-rs/lsd/pull/754
@sudame made their first contribution in https://github.com/lsd-rs/lsd/pull/787
@alexanderkjall made their first contribution in https://github.com/lsd-rs/lsd/pull/790
@Semnodime made their first contribution in https://github.com/lsd-rs/lsd/pull/805
@scarf005 made their first contribution in https://github.com/lsd-rs/lsd/pull/820
@CraigglesO made their first contribution in https://github.com/lsd-rs/lsd/pull/839
@hpwxf made their first contribution in https://github.com/lsd-rs/lsd/pull/822
@bells307 made their first contribution in https://github.com/lsd-rs/lsd/pull/856
@peppidesu made their first contribution in https://github.com/lsd-rs/lsd/pull/851
@jhalloy made their first contribution in https://github.com/lsd-rs/lsd/pull/861
@k4yt3x made their first contribution in https://github.com/lsd-rs/lsd/pull/852
@Marcos-Gamarra made their first contribution in https://github.com/lsd-rs/lsd/pull/871
Full Changelog: https://github.com/lsd-rs/lsd/compare/0.23.1...v1.0.0
-
- chocolatey-core.extension (≥ 1.3.5.1)
- vcredist140 (≥ 14.20.27508.1)
Ground Rules:
- This discussion is only about LSDeluxe (Portable) and the LSDeluxe (Portable) 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 LSDeluxe (Portable), 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.
Starz0r (maintainer) on 18 Sep 2023 19:21:51 +00:00:
User 'Starz0r' (maintainer) submitted package.
chocolatey-ops (reviewer) on 18 Sep 2023 20:00:11 +00:00:
lsd 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 18 Sep 2023 20:19:31 +00:00:
lsd has passed automated package testing (verification). The next step in the process is package scanning.
Please visit https://gist.github.com/choco-bot/45b91fbd05051a9766330efd2e2f201b for details.
This is an FYI only. There is no action you need to take.
chocolatey-ops (reviewer) on 18 Sep 2023 21:19:27 +00:00:
lsd 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 6 and 10 VirusTotal detections associated with it.
This package version cannot be approved without an exemption from a Moderator.
Starz0r (maintainer) on 25 Sep 2023 22:00:08 +00:00:
Rerun virus scanner.
Scanner Status Change - Virus Scanner has been set to rerun
chocolatey-ops (reviewer) on 25 Sep 2023 22:43:22 +00:00:
lsd 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 greater than 10 VirusTotal detections associated with it.
This package is now in a waiting state while you review the findings and provide an updated package, or send a message in the package review box on the package page.
Starz0r (maintainer) on 01 Oct 2023 02:39:51 +00:00:
Rerun virus scanner.
Scanner Status Change - Virus Scanner has been set to rerun
chocolatey-ops (reviewer) on 01 Oct 2023 02:41:06 +00:00:
lsd 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 greater than 10 VirusTotal detections associated with it.
This package is now in a waiting state while you review the findings and provide an updated package, or send a message in the package review box on the package page.
Starz0r (maintainer) on 07 Oct 2023 01:10:30 +00:00:
Rerun virus scanner.
Scanner Status Change - Virus Scanner has been set to rerun
chocolatey-ops (reviewer) on 07 Oct 2023 01:22:50 +00:00:
lsd 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 greater than 10 VirusTotal detections associated with it.
This package is now in a waiting state while you review the findings and provide an updated package, or send a message in the package review box on the package page.
chocolatey-ops (reviewer) on 08 Oct 2023 20:03:34 +00:00:
We've found lsd v1.0.0 in a submitted status and waiting for your next actions. It has had no updates for 20 or more days since a reviewer has asked for corrections. Please note that if there is no response or fix of the package within 15 days of this message, this package version will automatically be closed (rejected) due to being stale.
Take action:
If your package is failing automated testing, you can use the chocolatey test environment to manually run the verification and determine what may need to be fixed.
Note: We don't like to see packages automatically rejected. It doesn't mean that we don't value your contributions, just that we can not continue to hold packages versions in a waiting status that have possibly been abandoned. If you don't believe you will be able to fix up this version of the package within 15 days, we strongly urge you to log in to the site and respond to the review comments until you are able to.
Starz0r (maintainer) on 11 Oct 2023 22:17:51 +00:00:
User 'Starz0r' (maintainer) submitted package.
chocolatey-ops (reviewer) on 11 Oct 2023 22:53:18 +00:00:
lsd 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 11 Oct 2023 23:07:41 +00:00:
lsd has passed automated package testing (verification). The next step in the process is package scanning.
Please visit https://gist.github.com/choco-bot/b46eb096325d958449cf81542c493394 for details.
This is an FYI only. There is no action you need to take.
chocolatey-ops (reviewer) on 12 Oct 2023 00:04:26 +00:00:
lsd 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 greater than 10 VirusTotal detections associated with it.
This package is now in a waiting state while you review the findings and provide an updated package, or send a message in the package review box on the package page.
Starz0r (maintainer) on 20 Oct 2023 02:39:30 +00:00:
Rerun virus scanner.
Scanner Status Change - Virus Scanner has been set to rerun
chocolatey-ops (reviewer) on 20 Oct 2023 04:07:36 +00:00:
lsd 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 greater than 10 VirusTotal detections associated with it.
This package is now in a waiting state while you review the findings and provide an updated package, or send a message in the package review box on the package page.
Starz0r (maintainer) on 23 Oct 2023 02:39:34 +00:00:
Rerun virus scanner.
Scanner Status Change - Virus Scanner has been set to rerun
chocolatey-ops (reviewer) on 23 Oct 2023 02:56:21 +00:00:
lsd 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 greater than 10 VirusTotal detections associated with it.
This package is now in a waiting state while you review the findings and provide an updated package, or send a message in the package review box on the package page.
chocolatey-ops (reviewer) on 31 Oct 2023 22:55:22 +00:00:
We've found lsd v1.0.0 in a submitted status and waiting for your next actions. It has had no updates for 20 or more days since a reviewer has asked for corrections. Please note that if there is no response or fix of the package within 15 days of this message, this package version will automatically be closed (rejected) due to being stale.
Take action:
If your package is failing automated testing, you can use the chocolatey test environment to manually run the verification and determine what may need to be fixed.
Note: We don't like to see packages automatically rejected. It doesn't mean that we don't value your contributions, just that we can not continue to hold packages versions in a waiting status that have possibly been abandoned. If you don't believe you will be able to fix up this version of the package within 15 days, we strongly urge you to log in to the site and respond to the review comments until you are able to.
chocolatey-ops (reviewer) on 15 Nov 2023 22:56:56 +00:00:
Unfortunately there has not been progress to move lsd v1.0.0 towards an approved status within 15 days after the last review message, so we need to close (reject) the package version at this time. If you want to pick this version up and move it towards approval in the future, use the contact site admins link on the package page and we can move it back into a submitted status so you can submit updates.
Status Change - Changed status of package from 'submitted' to 'rejected'.
Pauby (reviewer) on 07 Dec 2023 10:53:33 +00:00:
Unrejecting as per request in Discord https://discord.com/channels/778552361454141460/897092000145350676/1182070935403118612
Status Change - Changed status of package from 'rejected' to 'submitted'.
Starz0r (maintainer) on 08 Dec 2023 08:04:09 +00:00:
User 'Starz0r' (maintainer) submitted package.
chocolatey-ops (reviewer) on 08 Dec 2023 08:39:20 +00:00:
lsd 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 08 Dec 2023 12:21:41 +00:00:
lsd has passed automated package testing (verification). The next step in the process is package scanning.
Please visit https://gist.github.com/choco-bot/88167d6e93ae8661373dfb5f228c9ffc for details.
This is an FYI only. There is no action you need to take.
chocolatey-ops (reviewer) on 08 Dec 2023 12:22:15 +00:00:
lsd 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 greater than 10 VirusTotal detections associated with it.
This package is now in a waiting state while you review the findings and provide an updated package, or send a message in the package review box on the package page.
chocolatey-ops (reviewer) on 28 Dec 2023 08:05:25 +00:00:
We've found lsd v1.0.0 in a submitted status and waiting for your next actions. It has had no updates for 20 or more days since a reviewer has asked for corrections. Please note that if there is no response or fix of the package within 15 days of this message, this package version will automatically be closed (rejected) due to being stale.
Take action:
If your package is failing automated testing, you can use the chocolatey test environment to manually run the verification and determine what may need to be fixed.
Note: We don't like to see packages automatically rejected. It doesn't mean that we don't value your contributions, just that we can not continue to hold packages versions in a waiting status that have possibly been abandoned. If you don't believe you will be able to fix up this version of the package within 15 days, we strongly urge you to log in to the site and respond to the review comments until you are able to.
Starz0r (maintainer) on 02 Jan 2024 02:16:20 +00:00:
User 'Starz0r' (maintainer) submitted package.
chocolatey-ops (reviewer) on 02 Jan 2024 03:03:47 +00:00:
lsd 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 02 Jan 2024 03:51:39 +00:00:
lsd has passed automated package testing (verification). The next step in the process is package scanning.
Please visit https://gist.github.com/choco-bot/9c72b224ec2c91ae9c0de048e22bf288 for details.
This is an FYI only. There is no action you need to take.
chocolatey-ops (reviewer) on 02 Jan 2024 03:53:57 +00:00:
lsd 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 greater than 10 VirusTotal detections associated with it.
This package is now in a waiting state while you review the findings and provide an updated package, or send a message in the package review box on the package page.
chocolatey-ops (reviewer) on 22 Jan 2024 02:19:31 +00:00:
We've found lsd v1.0.0 in a submitted status and waiting for your next actions. It has had no updates for 20 or more days since a reviewer has asked for corrections. Please note that if there is no response or fix of the package within 15 days of this message, this package version will automatically be closed (rejected) due to being stale.
Take action:
If your package is failing automated testing, you can use the chocolatey test environment to manually run the verification and determine what may need to be fixed.
Note: We don't like to see packages automatically rejected. It doesn't mean that we don't value your contributions, just that we can not continue to hold packages versions in a waiting status that have possibly been abandoned. If you don't believe you will be able to fix up this version of the package within 15 days, we strongly urge you to log in to the site and respond to the review comments until you are able to.
Starz0r (maintainer) on 05 Feb 2024 23:07:16 +00:00:
User 'Starz0r' (maintainer) submitted package.
chocolatey-ops (reviewer) on 05 Feb 2024 23:46:20 +00:00:
lsd 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 05 Feb 2024 23:57:09 +00:00:
lsd has passed automated package testing (verification). The next step in the process is package scanning.
Please visit https://gist.github.com/choco-bot/546e9839b7008abaa146d6248dc3dc22 for details.
This is an FYI only. There is no action you need to take.
chocolatey-ops (reviewer) on 06 Feb 2024 00:07:16 +00:00:
lsd 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 greater than 10 VirusTotal detections associated with it.
This package is now in a waiting state while you review the findings and provide an updated package, or send a message in the package review box on the package page.
chocolatey-ops (reviewer) on 25 Feb 2024 23:11:07 +00:00:
We've found lsd v1.0.0 in a submitted status and waiting for your next actions. It has had no updates for 20 or more days since a reviewer has asked for corrections. Please note that if there is no response or fix of the package within 15 days of this message, this package version will automatically be closed (rejected) due to being stale.
Take action:
If your package is failing automated testing, you can use the chocolatey test environment to manually run the verification and determine what may need to be fixed.
Note: We don't like to see packages automatically rejected. It doesn't mean that we don't value your contributions, just that we can not continue to hold packages versions in a waiting status that have possibly been abandoned. If you don't believe you will be able to fix up this version of the package within 15 days, we strongly urge you to log in to the site and respond to the review comments until you are able to.
Starz0r (maintainer) on 01 Mar 2024 22:23:01 +00:00:
User 'Starz0r' (maintainer) submitted package.
chocolatey-ops (reviewer) on 01 Mar 2024 23:02:41 +00:00:
lsd 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 23:45:33 +00:00:
lsd has passed automated package testing (verification). The next step in the process is package scanning.
Please visit https://gist.github.com/choco-bot/e26d1517478544b7ad407f3f11a80363 for details.
This is an FYI only. There is no action you need to take.
chocolatey-ops (reviewer) on 02 Mar 2024 00:41:38 +00:00:
lsd 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 greater than 10 VirusTotal detections associated with it.
This package is now in a waiting state while you review the findings and provide an updated package, or send a message in the package review box on the package page.
chocolatey-ops (reviewer) on 21 Mar 2024 22:26:42 +00:00:
We've found lsd v1.0.0 in a submitted status and waiting for your next actions. It has had no updates for 20 or more days since a reviewer has asked for corrections. Please note that if there is no response or fix of the package within 15 days of this message, this package version will automatically be closed (rejected) due to being stale.
Take action:
If your package is failing automated testing, you can use the chocolatey test environment to manually run the verification and determine what may need to be fixed.
Note: We don't like to see packages automatically rejected. It doesn't mean that we don't value your contributions, just that we can not continue to hold packages versions in a waiting status that have possibly been abandoned. If you don't believe you will be able to fix up this version of the package within 15 days, we strongly urge you to log in to the site and respond to the review comments until you are able to.
Starz0r (maintainer) on 25 Mar 2024 21:02:44 +00:00:
User 'Starz0r' (maintainer) submitted package.
chocolatey-ops (reviewer) on 25 Mar 2024 21:42:20 +00:00:
lsd has failed automated validation.
Requirements
Requirements represent the minimum quality of a package that is acceptable. When a package version has failed requirements, the package version requires fixing and/or response by the maintainer. Provided a Requirement has flagged correctly, it must be fixed before the package version can be approved. The exact same version should be uploaded during moderation review.
gep13 (reviewer) on 28 Mar 2024 13:33:00 +00:00:
Validation Status Change - Validation tests have been set to rerun.
chocolatey-ops (reviewer) on 28 Mar 2024 13:37:41 +00:00:
lsd 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 Mar 2024 13:57:16 +00:00:
lsd has passed automated package testing (verification). The next step in the process is package scanning.
Please visit https://gist.github.com/choco-bot/d52b9e31065146b68f5d52acfd619be7 for details.
This is an FYI only. There is no action you need to take.
chocolatey-ops (reviewer) on 28 Mar 2024 14:00:11 +00:00:
lsd 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 greater than 10 VirusTotal detections associated with it.
This package is now in a waiting state while you review the findings and provide an updated package, or send a message in the package review box on the package page.
chocolatey-ops (reviewer) on 22 Apr 2024 13:24:48 +00:00:
We've found lsd v1.0.0 in a submitted status and waiting for your next actions. It has had no updates for 20 or more days since a reviewer has asked for corrections. Please note that if there is no response or fix of the package within 15 days of this message, this package version will automatically be closed (rejected) due to being stale.
Take action:
If your package is failing automated testing, you can use the chocolatey test environment to manually run the verification and determine what may need to be fixed.
Note: We don't like to see packages automatically rejected. It doesn't mean that we don't value your contributions, just that we can not continue to hold packages versions in a waiting status that have possibly been abandoned. If you don't believe you will be able to fix up this version of the package within 15 days, we strongly urge you to log in to the site and respond to the review comments until you are able to.
Starz0r (maintainer) on 22 Apr 2024 20:13:04 +00:00:
User 'Starz0r' (maintainer) submitted package.
chocolatey-ops (reviewer) on 22 Apr 2024 20:46:30 +00:00:
lsd 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 22 Apr 2024 21:09:20 +00:00:
lsd has passed automated package testing (verification). The next step in the process is package scanning.
Please visit https://gist.github.com/choco-bot/454729e56f114bf81371a91a09330324 for details.
This is an FYI only. There is no action you need to take.
chocolatey-ops (reviewer) on 22 Apr 2024 21:20:53 +00:00:
lsd 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 greater than 10 VirusTotal detections associated with it.
This package is now in a waiting state while you review the findings and provide an updated package, or send a message in the package review box on the package page.