Built-Hidden Asset Finder avatar

Built-Hidden Asset Finder

Pricing

$0.25 / actor start

Go to Apify Store
Built-Hidden Asset Finder

Built-Hidden Asset Finder

Compare a file manifest or packaged project tree against its docs to surface built-but-undocumented scripts, pages, configs, and modules.

Pricing

$0.25 / actor start

Rating

0.0

(0)

Developer

theCR8Fconclave SYST3MS

theCR8Fconclave SYST3MS

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

13 days ago

Last modified

Share

Compare a supplied file manifest or packaged project tree against its documentation to find scripts, pages, configs, and modules that exist but are not represented in the docs.

Portable Apify input

Supply path and content records. Markdown files and records under docsPath form the documentation corpus.

{
"files": [
{"path": "docs/README.md", "content": "This repo documents the public API."},
{"path": "public-api.js", "content": "console.log('claimed')"},
{"path": "scripts/worker.py", "content": "print('built but undocumented')"}
],
"docsPath": "docs",
"maxFiles": 5000
}

For a prepared image or local run, omit files and provide rootPath instead. The verified synthetic manifest is in examples/sample-input.json.

What it returns

Each default-dataset item contains:

  • relative file path
  • broad file kind
  • whether the normalized file token appears in documentation
  • hidden score
  • normalized token used for comparison

OUTPUT.json also records the scan root/input mode, scanned-file count, hidden-file count, and all result items.

Use cases

  • AI-built repo verification
  • stale README and handoff checks
  • inherited-project inventory
  • technical diligence preparation
  • rebuild-prevention checks

Interpretation boundary

This is a fast filename-to-documentation comparison, not semantic code understanding. A result means “present but not named in the supplied docs,” not “malicious,” “unused,” or “secret.” Review findings before acting.

The run output exposes the default dataset plus OUTPUT.json in the default key-value store. Schemas live in .actor/output_schema.json and .actor/dataset_schema.json.