@plasmicapp/loader-nextjs MIT 10 versions

@plasmicapp/loader-nextjs

npm Repository Homepage

Plasmic loader SDK for Next.js

10

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

plasmicapp

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
bogus-package	bogus-package	AI (bogus-package): Established SDK package; sparse README/keywords are a style choice, not spam indicators.	ai	2026/05/31
phantom-deps	phantom-dep:@plasmicapp/watcher	AI (phantom-deps): First-party @plasmicapp scoped dep; used transitively in monorepo, not a phantom risk.	ai	2026/05/29
phantom-deps	phantom-dep:@plasmicapp/loader-core	AI (phantom-deps): First-party @plasmicapp scoped dep; used transitively in monorepo, not a phantom risk.	ai	2026/05/29
phantom-deps	phantom-dep:@plasmicapp/nextjs-app-router	AI (phantom-deps): First-party @plasmicapp scoped dep; used transitively in monorepo, not a phantom risk.	ai	2026/05/29

Versions (showing 10 of 10)

Version	Deps	Published
2.0.6	6 / 5	2026-05-29
2.0.5	6 / 5	2026-05-19
2.0.4	6 / 5	2026-05-13
2.0.3	6 / 5	2026-04-29
2.0.2	6 / 5	2026-04-20
2.0.1	6 / 5	2026-04-09
2.0.0	6 / 5	2026-03-25
1.0.456	6 / 3	2026-03-07
1.0.450	6 / 3	2026-01-14
1.0.446	6 / 3	2025-12-24

v2.0.6

1 finding

LOW No provenance attestation provenance

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

v2.0.5

1 finding

LOW No provenance attestation provenance

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

v2.0.4

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.

v2.0.3

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.

v2.0.2

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.

v2.0.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.

v2.0.0

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.

v1.0.456

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.

v1.0.450

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.

v1.0.446

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.