Is Container safe to use?

Container has an HVTrust score of 70.3/100 (Grade B), ranked #30 of 371 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Container?

Container scores 70.3/100 on HVTracker's evidence-weighted HVTrust scale. It has 351 GitHub stars and is categorized under Agent Skills.

Container

Repository

Website

Persistent Linux workspaces for agentic development.

Agent Skills TypeScript Listed BSD-3-Clause

Is Container safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 3.5 / 10

Provenance Attested

Signed commits 35%

Last push 11d ago

Advisories None known

Compare Container

How does it stack up against its Agent Skills neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Container scores 70.3/100 (Grade B), ranked #30 of 371 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 3.5/10; 35% of recent commits are signed; no published advisory affects its latest release (@aerovato/container); last pushed 2026-09-29. Every point is earned from checkable signals — never paid placement. How scoring works →

How Container could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Raise the OSSF Scorecard from 3.5 to 9.0lowest checks: CI-Tests 0, CII-Best-Practices 0, Code-Review 0 +11.5 → 81.8 A · #15 of 371
Sign every commit35% signed today +3.3 → 73.6 B · #27 of 371

Already done? Suggest a correction Add the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Container and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities and, for skills, AST02 Supply Chain Compromise.

Source Partly signed

github.com/aerovato/container, BSD-3-Clause, last pushed 2026-09-29. 35% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
Review and release Weak

OpenSSF Scorecard rates the repository's practices 3.5/10 (scanned Oct 7, 2026). The checks that decide who can get a change released:
- Code Review0
- Branch Protection3
- Signed Releases0
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies2
All 18 Scorecard checks

Binary-Artifacts 10

Branch-Protection 3

CI-Tests 0

CII-Best-Practices 0

Code-Review 0

Contributors 3

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 2

SAST 0

Security-Policy 0

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 0
Published packages Linked and attested
- npm @aerovato/container Source link points back to this repo Build provenance attested
What you install today No known advisories

Latest release checked: @aerovato/container 3.7.0. No published advisory affects it (OSV, checked 2026-10-10).

Changes to this chain

2026-09-23 Package provenance attestation detected
2026-08-28 OSSF Scorecard: 3.5/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

GitHub repository data
Package downloads
Supply-chain checks
Public actions (missing)
Community mentions (missing)

Verify this score yourself

Every build re-issues Container’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read the skill’s instructions for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you install it, such as Cisco Skill Scanner.

How Container compares in Agent Skills

Bars show each HVTrust score; the tick marks Container’s 70.3.

Where the 70.3 comes from

HVTrust dimensions vs the Agent Skills average

70.3 / 100 · 100.0% confidence

Container Agent Skills average (371 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

13.6 / 25

5.8 above avg 7.8

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

6.6 above avg 11.4

Transparency50% declared license · 50% OSSF Scorecard

11.5 / 17

0.5 below avg 12.0

Maintenance60% last-push freshness · 40% commit activity

14.6 / 20

in line with avg 14.1

AdoptionLog-scaled stars · package downloads

8.6 / 20

in line with avg 9.0

Quick Trust Read

What Would Improve It

Increase the share of verified signed commits for clearer maintainer identity.

Recent Changes

2026-09-24

Activity Score Changed

Activity score up 6pts (53 → 59)

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-23

Grade Changed

Trust grade D → B

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 3.5/10. Tighten the weakest checks to improve public safety evidence.

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

Compare with another agent Get email alerts for Container View Agent Skills Report missing data

56.4

Activity sub-score · out of 100

#30

In Agent Skills

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-09-29 2026-10-10

Activity & Reach

Stars

351

Forks

Last Push

2026-09-29

11 days ago

Commits (4 wk)

Downloads (7d)

npm

HN mentions (30d)

—

Open Issues

Rank Change

was #30

Analysis

Activity Inputs

56.4 / 100

StarsRepository reach

15.3 / 30

FreshnessLast push recency

23.5 / 25

ActivityRecent commits

10.5 / 25

CommunityFork signal

7.1 / 20

Common questions about Container

Container has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

Does Container publish package provenance?

Yes. Container's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does Container have an OpenSSF Scorecard?

Container has an OpenSSF Scorecard score of 3.5/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.

Is Container actively maintained?

Maintained. Last push was 11 days ago.

What license does Container use?

Container ships under BSD-3-Clause. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Container's commits signed?

35% of the last 100 commits to Container are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface

Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support

None detected

No MCP server signal detected.

Detailed evidence is not shown in the public view.

External Service Dependencies

None detected

No clear third-party provider dependency detected.

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

None detected

No clear plugin system or broad tool surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

high confidence

Match

Published package metadata matches the tracked repo

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

How this surface has changed

Detected changes to Container's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23

Provenance Added

Package provenance attestation detected

Maintain Container?

For maintainers

HVTrust scores Container from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-09-24

Activity Score Changed

Activity score up 6pts (53 → 59)

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-23

Grade Changed

Trust grade D → B

2026-09-23

Rank Moved

Rank rose 274 spots (#311 → #37)

2026-09-23

HVTrust Changed

HVTrust up 43.8pts (25.2 → 69.0)

2026-09-22

Newly Listed

First tracked at rank #311

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-08-28

Scorecard Added

OSSF Scorecard: 3.5/10

2026-08-28

Rank Moved

Rank rose 11 spots (#21 → #10)

2026-08-28

HVTrust Changed

HVTrust up 7.4pts (65.4 → 72.8)

2026-08-26

Newly Listed

First tracked at rank #19

GitHub → Website → npm: @aerovato/container

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/container.svg)](https://hvtracker.net/agents/container)
            
HTML:
            <a href="https://hvtracker.net/agents/container"><img src="https://hvtracker.net/badge/container.svg" alt="HVTrust"></a>

Other agents in Agent Skills

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON

Container

How Container could raise its score

Chain of custody

Source Partly signed

Review and release Weak

Published packages Linked and attested

What you install today No known advisories

Changes to this chain

Evidence behind this score

Verify this score yourself

What this score doesn’t check

How Container compares in Agent Skills

Where the 70.3 comes from

HVTrust dimensions vs the Agent Skills average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about Container

AI agent surface

Maintain Container?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in Agent Skills