registry / @posterna/next / 0.1.1
@posterna/next@0.1.1
Next.js integration for Posterna: verify AI agents and crawlers and apply policy.
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe package has no install hooks, and its runtime behavior matches its stated Next.js verification purpose. Its core documents the counter data and destination, and sends no counters without a configured site key.
Static reason
No blocking static signals were detected.
Trigger
Creating a Posterna instance or handling a request through the middleware.
Impact
No malicious impact identified; counter data is documented as aggregated and excludes addresses, URLs, and header values.
Mechanism
Reads the configured policy file, refreshes signed directory data from its service, and sends aggregated counters there only when a site key is configured.
AI rationale
The package has no install hooks, and its runtime behavior matches its stated Next.js verification purpose. Its core documents the counter data and destination, and sends no counters without a configured site key.
Evidence
agents.yaml (read by default when creating an instance)
Network endpoints1
posterna.com/v1/
Decision evidence
public snapshotAI called this Clean at 96.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest has no install lifecycle hooks; its scripts are build and typecheck.
- The adapter reads the policy file when configured and sets up counters as part of creating a Posterna instance.
- The core documents that counters send aggregated request counts only with POSTERNA_SITE_KEY; without a key they send nothing, and do not retain or send addresses, URLs, or header values.
- The core’s default service URL is https://posterna.com/v1/, used for directory refresh and counters ingestion.
Evidence against
Behavioral surface
Filesystem
Source & flagged code
5 flaggedpackage.jsonView file
56"dependencies": {
"@posterna/core": "0.1.1"
},
"devDependencies": {
"next": "16.4.3",
"react": "19.3.1",
"react-dom": "19.3.1"
},
"peerDependencies": {
"next": "^15.0.0 || ^16.0.0"
},
"scripts": {
"buil
Low
Suspicious Lifecycle Evidence
The manifest has no install lifecycle hooks; its scripts are build and typecheck.
package.jsonView on unpkg · L56dist/index.jsView file
44const full = file.startsWith("/") ? file : `${process.cwd()}/${file}`;
try {
return { text: fs.readFileSync(full, "utf8"), problem: null };
} catch (error) {
const problem = error.code === "ENOENT" ? `No policy file at ${full}. Every request is allowed and labeled. Run \`npx posterna init\` to create one.` : `Could not read ${full} (${message(error)}). Every request is allowed and la
Low
Ai Review Evidence
The adapter reads the policy file when configured and sets up counters as part of creating a Posterna instance.
dist/index.jsView on unpkg · L44Findings
7 Low
LowScripts Present
LowFilesystem
LowSuspicious Lifecycle Evidencepackage.json
LowAi Review Evidencedist/index.js
LowAi Review Evidence.lpm-dependency-evidence-655c8920-e9f0-4823-8c61-fe2ce2063a89/0/npm-linux/README.md
LowAi Review Evidence.lpm-dependency-evidence-655c8920-e9f0-4823-8c61-fe2ce2063a89/0/npm-linux/dist/index.js
LowAi Review Evidence.lpm-dependency-evidence-655c8920-e9f0-4823-8c61-fe2ce2063a89/0/npm-linux/dist/index.js
Affected versions and remediation
This report applies to @posterna/next@0.1.1.
See all versions of @posterna/next for other recorded verdicts.
- Review the evidence and your use of @posterna/next@0.1.1 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.