Creator Portal reports "tests failed" but `scan-community-package` passes on the published package

Questions
1

Describe the problem/error/question

I’m submitting @aws/n8n-nodes-agentcore (an AWS-published community node) for
verification through the Creator Portal. The portal reports that tests failed and
tells me to run npx @n8n/scan-community-package for details — but running that
exact command on the published package passes all checks. I can’t reproduce any
failure with the published tooling.

This looks like the same Creator Portal false-rejection a couple of other
submitters reported recently (CLI scanner passes, portal fails, traced to the
verification tool’s release pipeline rather than the package). Could someone from
the node review team take a look and do a manual re-check / advance for
@aws/n8n-nodes-agentcore@0.3.2? Everything on my side checks out (details below).

Package:

Things I’ve already ruled out on my side:

  • Published a new version (0.3.2) after my last fix
  • No versions unpublished/deprecated (all versions still resolve)
  • Repository URL points at the public GitHub repo
  • Ran @n8n/scan-community-package@latest to rule out a cached scanner — still passes
  • Also ran the full @n8n/eslint-plugin-community-nodes rule set directly against
    the tarball — clean, zero violations

What is the error message (if any)?

Creator Portal:

Changes required to your node package
Some of the tests have failed, please run npx @n8n/scan-community-package @aws/n8n-nodes-agentcore for more details.

Actual output of that command on the published package:

Checking provenance for @aws/n8n-nodes-agentcore@0.3.2...✅ Provenance check passed
Downloading @aws/n8n-nodes-agentcore@0.3.2...✅ Downloaded
Analyzing @aws/n8n-nodes-agentcore@0.3.2...✅ Analyzed
✅ Package @aws/n8n-nodes-agentcore@0.3.2 has passed all security checks

(scan-community-package 0.27.1, run with @latest.)

Please share your workflow

N/A — this is a node verification/submission issue, not a workflow issue.

Share the output returned by the last node

N/A — see the scanner output above.

Information on your n8n setup

  • n8n version: N/A (Creator Portal submission for @aws/n8n-nodes-agentcore@0.3.2; also tested on self-hosted latest)
  • Database (default: SQLite): SQLite
  • n8n EXECUTIONS_PROCESS setting (default: own, main): default
  • Running n8n via (Docker, npm, n8n cloud, desktop app): npm (self-hosted) for local testing; Creator Portal for verification
  • Operating system: macOS
3

Thanks for letting us know about this, We have created NODE-5524 as the internal dev ticket to look into it.

4

@rsundaraws Can you try running the scan tool using the @beta version? There was an issue with the tags on the tool and the wrong version was tagged as latest.

5

thanks so much for the fast support on the scanner tag issue :folded_hands: Once I ran against @beta I caught the real lint findings, fixed them all, and @aws/n8n-nodes-agentcore@0.3.3 now passes the scanner cleanly. Verification is submitted.

Really appreciate your help !!

6

Thanks for pointing me to the @beta scanner. I ran the latest stable release (0.27.1), which passed all checks, so I’ll test with the beta version as well.

If the beta scanner reports additional issues, I’ll update this thread with the output. If it also passes, that would suggest the Creator Portal is still using an older or different validation pipeline, and the failure is likely on the portal side rather than with the package itself.

Thanks for looking into NODE-5524—I’ll share the beta scan results once I have them.

If you’re looking for the actual command to verify with the beta scanner, run:



npx @n8n/scan-community-package@beta @aws/n8n-nodes-agentcore

If that also passes, include the full output in your reply, for example:



Checking provenance... ✅
Downloading package... ✅
Analyzing package... ✅
Package @aws/n8n-nodes-agentcore@0.3.2 passed all security checks.

At that point, you have strong evidence that the issue is with the Creator Portal’s verification pipeline rather than your package, and the n8n team can manually re-run the verification or wait for the fix associated with NODE-5524.

7

@shedrach We had already solved this one as we knew where the issue was.