Digital Marketing Pro

An open-source AI based digital marketing operating system for strategy, SEO, AEO/GEO, paid media, content, CRM, and analytics - grounded in brand context, human approval, and verifiable outputs. Best for Brands, Agencies and one person campanies.

Agent Skills Python Listed MIT

Is Digital Marketing Pro safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 4.1 / 10
Provenance None
Signed commits 1%
Last push 8d ago
Compare Digital Marketing Pro
Suggest a correction

In detail: Digital Marketing Pro scores 52.4/100 (Grade C), ranked #229 of 396 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.1/10; 1% of recent commits are signed; last pushed 2026-11-07. Every point is earned from checkable signals — never paid placement. How scoring works →

How Digital Marketing Pro 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.

Chain of custody

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

  1. Source Partly signed

    github.com/indranilbanerjee/digital-marketing-pro, MIT, last pushed 2026-11-07. 1% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 4.1/10 (scanned Nov 15, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection3
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies1
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 3
    CI-Tests -1
    CII-Best-Practices 0
    Code-Review 0
    Contributors 6
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 10
    Packaging -1
    Pinned-Dependencies 1
    SAST 0
    Security-Policy 10
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 0
  3. Published packages None

    No registry package. Digital Marketing Pro is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

  • 2026-08-27 OSSF Scorecard: 4.6/10

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

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

Verify this score yourself

Every build re-issues Digital Marketing Pro’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.

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 Digital Marketing Pro compares in Agent Skills

  1. #227 Han 52.5 +0.1
  2. #228 Swift Concurrency Agent Skill 52.5 +0.1
  3. #229 Digital Marketing Pro 52.4 this agent
  4. #230 Claude Code Guide 52.4 ±0
  5. #231 Garden Skills 52.4 ±0

Bars show each HVTrust score; the tick marks Digital Marketing Pro’s 52.4.

Where the 52.4 comes from

HVTrust dimensions vs the Agent Skills average

52.4 / 100 · 100.0% confidence

Digital Marketing Pro Agent Skills average (396 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
5.2 / 25
3.0 below avg 8.2
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.7 below avg 11.5
Transparency50% declared license · 50% OSSF Scorecard
12.0 / 17
in line with avg 12.2
Maintenance60% last-push freshness · 40% commit activity
17.8 / 20
3.8 above avg 14.0
AdoptionLog-scaled stars · package downloads
7.2 / 20
2.0 below avg 9.2

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-11-10
Rank Moved
Rank dropped 13 spots (#212 → #225)
2026-10-28
Rank Moved
Rank rose 10 spots (#209 → #199)
2026-10-27
Rank Moved
Rank rose 30 spots (#239 → #209)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.1/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Compare with another agent
View Agent Skills Report missing data
71.8
Activity sub-score · out of 100
#229

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

Signals refreshed 2026-11-15 04:07 UTC · Repo last pushed 8 days ago

Rank Trend

2026-09-29 2026-11-15

Activity & Reach

Stars
957
Forks
158
Last Push
2026-11-07
8 days ago
Commits (4 wk)
37
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
1
Rank Change
▲1
was #230

Analysis

Activity Inputs

71.8 / 100
StarsRepository reach
17.9 / 30
FreshnessLast push recency
23.9 / 25
ActivityRecent commits
19.7 / 25
CommunityFork signal
10.2 / 20

Common questions about Digital Marketing Pro

Public trust evidence for Digital Marketing Pro is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does Digital Marketing Pro publish package provenance?
No published build provenance is currently detected for Digital Marketing Pro. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Digital Marketing Pro have an OpenSSF Scorecard?
Digital Marketing Pro has an OpenSSF Scorecard score of 4.1/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 Digital Marketing Pro actively maintained?
Maintained. Last push was 8 days ago.
What license does Digital Marketing Pro use?
Digital Marketing Pro ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Digital Marketing Pro's commits signed?
1% of the last 100 commits to Digital Marketing Pro 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
medium confidence
Implemented
Digital Marketing Pro appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
3 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
  • shell
Detailed evidence is not shown in the public view.
Package Provenance Drift
N/A
No package source configured
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 Digital Marketing Pro'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-10-05
Mcp Status Changed
Detected MCP server support changed: declared → implemented
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependencies: Anthropic, Google Gemini, OpenAI
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → declared

Maintain Digital Marketing Pro?

For maintainers

HVTrust scores Digital Marketing Pro 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.

Reputation Timeline

Signal history
Rank 21HVTrust 3MCP 2Scorecard 1Delisted 1Listed 1Surface 1Surface 1Score 1Grade 1
2026-11-10
Rank Moved
Rank dropped 13 spots (#212 → #225)
2026-10-28
Rank Moved
Rank rose 10 spots (#209 → #199)
2026-10-27
Rank Moved
Rank rose 30 spots (#239 → #209)
2026-10-13
Rank Moved
Rank dropped 10 spots (#196 → #206)
2026-10-11
Rank Moved
Rank rose 24 spots (#219 → #195)
2026-10-10
Grade Changed
Trust grade D → C
2026-10-10
Rank Moved
Rank rose 30 spots (#249 → #219)
2026-10-05
Mcp Status Changed
Detected MCP server support changed: declared → implemented
2026-10-05
Rank Moved
Rank rose 28 spots (#278 → #250)
2026-10-04
Rank Moved
Rank rose 13 spots (#291 → #278)
2026-10-04
Activity Score Changed
Activity score up 9pts (55 → 64)
2026-09-25
Rank Moved
Rank rose 50 spots (#331 → #281)
2026-09-25
HVTrust Changed
HVTrust up 16.1pts (29.7 → 45.8)
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependencies: Anthropic, Google Gemini, OpenAI
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → declared
2026-09-23
Rank Moved
Rank dropped 35 spots (#297 → #332)
2026-09-23
HVTrust Changed
HVTrust up 3.1pts (26.6 → 29.7)
2026-09-22
Newly Listed
First tracked at rank #297
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-10
Rank Moved
Rank dropped 10 spots (#303 → #313)
2026-09-05
Rank Moved
Rank dropped 11 spots (#277 → #288)
2026-09-03
Rank Moved
Rank dropped 13 spots (#256 → #269)
2026-09-02
Rank Moved
Rank dropped 13 spots (#243 → #256)
2026-09-01
Rank Moved
Rank dropped 13 spots (#230 → #243)
2026-08-31
Rank Moved
Rank dropped 19 spots (#211 → #230)
2026-08-30
Rank Moved
Rank dropped 36 spots (#175 → #211)
2026-08-29
Rank Moved
Rank dropped 40 spots (#135 → #175)
2026-08-28
Rank Moved
Rank dropped 24 spots (#111 → #135)
2026-08-27
Scorecard Added
OSSF Scorecard: 4.6/10
2026-08-27
Rank Moved
Rank rose 197 spots (#308 → #111)
2026-08-27
HVTrust Changed
HVTrust up 17.9pts (14.8 → 32.7)
2026-08-26
Rank Moved
Rank dropped 157 spots (#151 → #308)

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 52.4 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/digital-marketing-pro.svg)](https://hvtracker.net/agents/digital-marketing-pro)
HTML:
<a href="https://hvtracker.net/agents/digital-marketing-pro"><img src="https://hvtracker.net/badge/digital-marketing-pro.svg" alt="HVTrust"></a>

Other agents in Agent Skills

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