Skip to content
Back to skills

Angular Upgrade Libraries Angular View Engine Library Audit V13

ASecurity

Audit Angular libraries for View Engine compatibility before Angular 13 or later. Use when package dependencies may still require ngcc or old metadata formats.

  • 4 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 2, 2026
developmenttypescriptgoangular

Security analysis

A100/100

Scanned October 2, 2026

npx -y skills add janpereira-dev/ngAutoPilot --skill angular--upgrade--libraries--angular-view-engine-library-audit-v13 --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Angular Upgrade Libraries Angular View Engine Library Audit V13?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Angular  Upgrade  Libraries  Angular View Engine Library Audit V13
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/janpereira-dev-angular-upgrade-libraries-angular-view-engine-libr/badge)](https://www.skillsdirectory.com/skills/janpereira-dev-angular-upgrade-libraries-angular-view-engine-libr)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
id: angular.upgrade.libraries.angular-view-engine-library-audit-v13
name: Angular View Engine Library Audit v13
description: >
  Audit Angular libraries for View Engine compatibility before Angular 13 or later. Use when package dependencies may still require ngcc or old metadata formats.
stack:
  - Angular
  - TypeScript
category: libraries
status: stable
version: 0.10.0
owner: NgAutoPilot
triggers:
  - View Engine library audit
  - ngcc audit
  - Angular library compatibility
compatibility:
  angular:
    min: "13"
---

# Angular View Engine Library Audit v13

## Purpose

Audit libraries for View Engine compatibility.

## When to Use

- The project depends on third-party Angular libraries.
- The upgrade path may cross Angular 13.

## When Not to Use

- No Angular libraries are present.
- Library compatibility is already known.

## Required Inputs

- package.json
- lockfile
- library metadata

## Procedure

1. Identify library packages.
2. Check for View Engine or ngcc dependence.
3. Block or approve the upgrade.

## Do

- Keep compatibility explicit.
- Document library risk.

## Do Not

- Do not assume libraries are Ivy-compatible.

## Review Checklist

- [ ] Library list is known.
- [ ] View Engine risk checked.
- [ ] Decision recorded.

## Expected Output

1. Library audit summary.
2. Blockers list.

## Exit Criteria

- Library compatibility is explicit.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…