@notion-kit/single-image-dropzone No license 13 versions

@notion-kit/single-image-dropzone

npm Repository Homepage

13

Versions

—

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

steeeee0223

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:@notion-kit/cn	AI (phantom-deps): Same-org monorepo sibling; phantom-dep fires due to re-export pattern, not a real missing import.	ai	2026/05/20
dependencies	unvetted-dep:@notion-kit/cn	AI (dependencies): Sibling package in the same notion-kit monorepo; co-versioned at 0.17.0, expected dependency.	ai	2026/05/19
dependencies	unvetted-dep:@notion-kit/shadcn	AI (dependencies): Sibling package in the same notion-kit monorepo; co-versioned at 0.17.0, expected dependency.	ai	2026/05/19

Versions (showing 13 of 13)

Version	Deps	Published
0.17.0	4 / 10	2026-04-30
0.16.0	4 / 10	2026-03-13
0.15.1	4 / 10	2026-02-01
0.15.0	4 / 10	2026-01-28
0.11.0	5 / 9	2025-11-06
0.10.0	5 / 9	2025-09-06
0.9.0	5 / 9	2025-08-06
0.8.0	5 / 9	2025-07-09
0.7.0	5 / 9	2025-06-04
0.6.1	5 / 9	2025-06-02
0.6.0	5 / 9	2025-05-31
0.5.0	5 / 9	2025-05-11
0.4.0	5 / 9	2025-05-09

v0.17.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.

v0.16.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.

v0.15.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.

v0.15.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.

v0.11.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.

v0.10.0

1 finding

LOW No provenance attestation provenance

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

v0.9.0

1 finding

LOW No provenance attestation provenance

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

v0.8.0

1 finding

LOW No provenance attestation provenance

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

v0.7.0

1 finding

LOW No provenance attestation provenance

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

v0.6.1

1 finding

LOW No provenance attestation provenance

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

v0.6.0

1 finding

LOW No provenance attestation provenance

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

v0.5.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.

v0.4.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.