The License Block policy prevents addition of packages with specific open source licenses to a registry.
This enables registries where specific open source licenses are blocked, ensuring license compliance from problematic licenses.
Read moreThe open source licenses information available for packages in Bytesafe has been extended, with:
package.json metadataBig release that adds Dashboards in Bytesafe. All security issues, license issues and other relevant metrics from your registries in one place.
Bytesafe has also been completely redesigned to greatly improve the user experience across all devices.
Read moreThe package license information available for packages stored in Bytesafe registries has been extended with package license analysis.
In addition to the licenses defined in package.json, Bytesafe will now scan packages and identify licenses information in other package files as well.
Two new policies have been added to Bytesafe: Block and Allow-only. Both policies are used to enforce control over what packages or package versions are allowed in a registry.
The Block policy prevents specific packages from being added to a registry. Just the opposite, the Allow-only policy is used to only allow specific packages in a registry.
Read moreThe License scanner plugin scans all packages in a registry and flags potential license issues.
Issues flagged by the scanner are displayed in Bytesafe and notifications will be sent to the configured Slack channels.
Read moreBytesafe now offers support for integration with Git repositories as upstreams to your registries.
This feature allows users to connect private and public Git repositories to Bytesafe as package sources. For the developer this means that node modules can be installed regardless if they are sourced from your private registry, an external npm registry or Git repository.
Bytesafe plugins and policies can also be applied on modules sourced from Git repositories.
Read moreBytesafe’s documentation site is now live! This is our resource for technical documentation on how to use Bytesafe.
The documentation will be the default resource to visit for users that have questions on how to use the Bytesafe product and will complement the blog.
Read moreBytesafe now supports read-only tokens. For example, these can be used in CI/CD pipelines where you only require read access or similar use cases.
Read moreThe Teams plan enables teams management, basic access control, Slack integration and full access to all our plugins and policies.
Read moreThe release brings Security Scanning features to Bytesafe registries, by adding a Vulnerability Scanner plugin and three security related policies.
We are also releasing a Slack integration which allows you to be notified when new vulnerabilities are found in your workspace.
Read moreTwo main features of the release related to release management: Promote functionality for package versions as well as Version auto increment plugin has been added.
Promote package, lets you select a existing package version and promote it to a new version (and possible new target registry), removing the need to re-publish from your project and running the risk of including unplanned changes.
Read moreThe npm deprecate command is now supported with Bytesafe registries.
Additionally, deprecate information linked to the package version is now available as output when using npm install and bytesafe push / pull.
Information regarding deprecated package versions is also available in the Bytesafe web application.
Read moreMain feature added by the release is a Bytesafe CLI for the Windows OS. Bytesafe CLI is available for download from the CLI page of the Bytesafe documentation.
Release notes:
npm whoami, ping, audit, logout, token commandsyarn commandsWe are happy to introduce Policies & Plugins for Bytesafe registries:
The main feature of the initial release is to provide private registry functionality, including: