@vercel/webpack-asset-relocator-loader MIT 25 versions

@vercel/webpack-asset-relocator-loader

npm Repository Homepage

Asset relocation loader used in ncc for performing Node.js builds while emitting and relocating any asset references.

25

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

matheusschriswdmrnick.traceymatt.strakavercel-release-botquietshuijjkzeit-bot

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:resolve-from	AI (phantom-deps): resolve-from is a declared runtime dep; phantom-dep false positive likely due to indirect usage or config-level reference in this build tool.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): Publisher change from styfle to zeit-bot reflects Vercel's organizational transition; zeit-bot is the official Vercel automation account with a strong track record across hundreds of packages.	ai	2026/04/24
semgrep	semgrep:eval-usage	AI (semgrep): eval("require.resolve(...)") is a documented bundler technique to prevent static capture of require calls; consistent with this package's asset relocation purpose across all versions.	ai	2026/04/23
dependencies	unvetted-dep:node-gyp-build	AI (dependencies): node-gyp-build is a well-established native addon loader; its use is appropriate for a webpack asset relocator that handles native binaries.	ai	2026/04/23
maintainer-change	maintainer-removed	AI (maintainer-change): Removals alongside additions in a large org like Vercel reflect normal team churn, not a takeover signal.	ai	2026/04/23
publish-pattern	new-deps-added	AI (publish-pattern): 'resolve' is a well-established module resolution library; its addition is consistent with the build script change externalizing it (-e resolve flag in ncc build).	ai	2026/04/23
maintainer-change	maintainer-added	AI (maintainer-change): Vercel is a large org; maintainer roster changes reflect normal team rotation. Published by vercel-release-bot with a strong track record across the Vercel ecosystem.	ai	2026/04/23

Versions (showing 25 of 25)

Version	Deps	Published
1.10.0	16 / 7	2025-07-10
1.9.1	1 / 22	2025-07-10
1.9.0	1 / 22	2025-07-04
1.8.0	1 / 22	2025-07-03
1.7.5	1 / 22	2025-07-03
1.7.4	1 / 23	2024-05-16
1.7.3	1 / 23	2022-07-13
1.7.2	0 / 24	2022-03-22
1.7.1	0 / 24	2022-03-22
1.7.0	0 / 24	2021-08-19
1.6.0	0 / 24	2021-07-06
1.5.0	0 / 24	2021-06-10
1.4.1	0 / 23	2021-05-27
1.4.0	0 / 23	2021-04-27
1.3.1	0 / 23	2021-04-20
1.3.0	0 / 23	2021-04-05
1.2.4	0 / 23	2021-03-22
1.2.3	0 / 26	2021-03-13
1.2.2	0 / 26	2021-03-11
1.2.1	0 / 26	2021-01-11
1.2.0	0 / 26	2021-01-11
1.1.1	0 / 26	2021-01-10
1.1.0	0 / 26	2021-01-05
1.0.0	0 / 26	2020-12-18
0.9.1	0 / 24	2020-12-15

v1.10.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.9.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.9.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.8.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.1

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: zeit-bot → vercel-release-bot (on 2022-03-22) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2022-03-22. This could indicate a legitimate maintainer transition or an account compromise.

v1.7.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.6.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.5.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.0

2 findings

HIGH Publisher changed: styfle → zeit-bot (on 2020-12-18) provenance

This version was published by a different npm account than previous versions on 2020-12-18. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.