Linux workstation

Upstream software project

velocity

Java-based template engine for web application

About velocity

Java-based template engine for web application

This project links 3 native package records across 2 recorded operating-system releases. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Project pictures and package coverage

Debian 12 (Bookworm): 2 package records; Debian 13 (Trixie): 1 package records. Catalog coverage diagram, not an application screenshot.velocity: recorded package coverageDebian 12 (Bookworm)2 recordsDebian 13 (Trixie)1 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
velocity
Publisher
Not authoritatively mapped
Native package records
3
Operating systems
debian-12, debian-13
License expression
Not reported
Metadata completeness
80/100 (not a software quality rating)
Source repository
Not reported

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

Java-based template engine for web application

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

Debian 12 (Bookworm)

  1. velocity

    Debian 12 (Bookworm) / java

    1.7-6

    Java-based template engine for web application

    allbookworm
  2. velocity-doc

    Debian 12 (Bookworm) / doc / source velocity

    1.7-6

    Documentation for velocity

    allbookworm

Debian 13 (Trixie)

  1. velocity

    Debian 13 (Trixie) / java

    1.7-7

    Java-based template engine for web application

    alltrixie

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.