
Research
/Security News
5 Malicious Rust Crates Posed as Time Utilities to Exfiltrate .env Files
Published late February to early March 2026, these crates impersonate timeapi.io and POST .env secrets to a threat actor-controlled lookalike domain.
@tapjs/after
Advanced tools
@tapjs/afterA default tap plugin providing t.after() and t.teardown().
This plugin is installed with tap by default. If you had
previously removed it, you can tap plugin add @tapjs/after to
bring it back.
import t from 'tap'
t.after(() => {
// this will run after all the tests in this file are done
})
The method can be called as either t.teardown() or t.after().
In an earlier version of tap, these had slightly different
behaviors, but they are now the same.
If the method returns a promise, it will be awaited before moving on to the next test.
So, this test:
import t from 'tap'
t.test('first test', t => {
t.teardown(async () => {
// this will wait before moving on
await new Promise(res => setTimeout(res, 100))
console.error('end of first test teardown')
})
console.error('in first test')
t.end()
})
t.test('second test', t => {
console.error('in second test')
t.end()
})
will print:
in first test
end of first test teardown
in second test
If multiple teardown methods are assigned to a single test, they
will be run in reverse order of how they are assigned. This is
a change from earlier versions of tap, and provides symmetry with
t.before().
In practice, it can make things more straightforward, by keeping cleanup methods close to their associated setup logic. For example:
const connection = await connectToDB()
t.ok(connection, 'connected to database')
t.teardown(() => disconnectFromDB(connection))
const user1 = await createUser(connection)
t.ok(user1, 'created user 1')
t.teardown(() => deleteUser(connection, user1))
const user2 = await createUser(connection)
t.ok(user2, 'created user 2')
t.teardown(() => deleteUser(connection, user2))
If we delete the connection created in the first step before deleting the user records, then we can't use that connection to delete the user records.
This can also be accomplished with subtests, and a single teardown in each section:
t.test('user db tests', async t => {
const connection = await connectToDB()
t.ok(connection, 'connected to database')
t.teardown(() => disconnectFromDB(connection))
t.test('user 1', async t => {
const user1 = await createUser(connection)
t.ok(user1, 'created user 1')
t.teardown(() => deleteUser(connection, user1))
})
t.test('user 2', async t => {
const user2 = await createUser(connection)
t.ok(user2, 'created user 2')
t.teardown(() => deleteUser(connection, user2))
})
})
FAQs
a built-in tap extension for t.after() and t.teardown()
The npm package @tapjs/after receives a total of 183,030 weekly downloads. As such, @tapjs/after popularity was classified as popular.
We found that @tapjs/after demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 2 open source maintainers collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Research
/Security News
Published late February to early March 2026, these crates impersonate timeapi.io and POST .env secrets to a threat actor-controlled lookalike domain.

Security News
A recent burst of security disclosures in the OpenClaw project is drawing attention to how vulnerability information flows across advisory and CVE systems.

Research
/Security News
Mixed-script homoglyphs and a lookalike domain mimic imToken’s import flow to capture mnemonics and private keys.