In response to your requests, we've introduced a new way for you to send data to us via a URL. Your feedback is invaluable to us, and we're always striving to meet your needs.

With this innovative approach, you can conveniently send us the URL of a preexisting resource, and we will take care of the rest, downloading and scanning it for you.

cho https://packetly.com | aws s3 cp - s3://packetly/test/file.txt --endpoint-url https://demo.pcktly.com --metadata="uploader=url"

The URL is sent as the body of the upload request and a new bit of meta data is set to tell us it's a URL uploader.

This metadata feature is a security measure to prevent customers from uploading files containing URLs. It will only download the file if you explicitly set the uploader to the URL.

In the dashboard file, reports will now contain an upload type. We hope to add more types going forwards.

We have fixed several annoying bugs related to the UI on the platform.

• Fixed a navigation bug on mobile.
• Fixed the NSFW accuracy range slider not updating correctly.
• Added missing breadcrumbs in the UI
• The Endpoint Creation page only includes credentials with secrets

Nice to haves:

• Added Packetly Logo to emails
• New Email notification channels require email verification to help users confirm they set it up correctly (And protect our deliverability as a platform)

We also updated the pricing page to have a interactive slider to help you understand the real costs of the platform.

What team does not want more slack notifications? We are proud to announce we have added support for Slack notifications.

We support on demand for content warnings, but also if you have a-lot of shady content been scanned daily, weekly and monthly roundups.

As with email notifications, the channel is configured on a per endpoint basis (we did this to allow you to set a endpoint per client for example).

Add Slack Nofications to endpoint

Then you can enjoy notifications

example slack notifications

The Remember me was not working on login; how annoying!

Well, it's all working as expected now.

Clients can now send AWS metadata 'client-ip' to track the IP address of the user who uploaded the asset. Useful for tracking patterns in users patterns.

Example

echo 'X5O!P%@AP[4\PZX54(P^)7CC)7}$EICAR-STANDARD-ANTIVIRUS-TEST-FILE!$H+H*' | 
aws s3 cp - s3://packetly/test/file.txt --endpoint-url https://yourendpoint.pcktly.com --metadata "client-ip=1.1.1.1"

We plan to add the ability to filter by this in the future.

We decided the best way to keep everyone updated with news and topics was to create a blog

We want to keep everyone updated with our fast development pace. However, we have to start somewhere.

Foundation

• Malware Scanner
• NSFW Image Scanner
• Email Notifications
• Teams
• Billing