with
Compile time `with` for strict mode JavaScript
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are legitimate @babel/* ecosystem packages replacing old babylon/* equivalents — a standard migration, not an attack vector. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change from forbeslindesay to with-bot reflects a legitimate org bot account transition for the pugjs ecosystem; repo URL confirms pugjs/with ownership. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): with-bot is a pugjs org bot account, consistent with legitimate maintainer transition; no compromise indicators. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase explained by TypeScript migration and switch from lexical-scope to Babel AST tooling; no obfuscation or injected payloads. | ai | |
| typosquat | typosquat.levenshtein:vite | AI (typosquat): Package name 'with' is a legitimate JavaScript keyword; the package's documented purpose is compile-time 'with' support. Levenshtein distance to 'vite' is coincidental, not indicative of typosquatting. | ai | |
| dependencies | unvetted-dep:assert-never | AI (dependencies): assert-never is a well-known TypeScript exhaustiveness utility; unvetted status is a pipeline artifact. | ai | |
| dependencies | unvetted-dep:babel-walk | AI (dependencies): babel-walk is a legitimate pugjs/Babel AST traversal utility; unvetted status is a pipeline artifact. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 7.0.2 | 4 / 8 | |
| 7.0.1 | 4 / 8 | |
| 7.0.0 | 4 / 8 | |
| 6.0.0 | 4 / 6 | |
| 5.1.1 | 2 / 2 | |
| 5.1.0 | 2 / 2 | |
| 5.0.2 | 2 / 2 | |
| 5.0.1 | 2 / 2 | |
| 5.0.0 | 2 / 2 | |
| 4.0.3 | 2 / 2 | |
| 4.0.2 | 2 / 2 | |
| 4.0.1 | 2 / 2 | |
| 4.0.0 | 2 / 2 | |
| 3.0.1 | 1 / 1 | |
| 3.0.0 | 1 / 1 | |
| 2.0.0 | 1 / 1 | |
| 1.1.1 | 1 / 1 | |
| 1.1.0 | 1 / 1 | |
| 1.0.4 | 1 / 1 | |
| 1.0.3 | 1 / 1 | |
| 1.0.2 | 1 / 1 | |
| 1.0.1 | 1 / 1 | |
| 1.0.0 | 1 / 1 |
v7.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
2 findingsThis version was published by a different npm account than previous versions on 2020-05-25. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.