← Home

@notion-kit/tags-input

16
Versions
MIT
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

steeeee0223

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): No provenance across all @notion-kit/* packages; consistent publishing pattern. ai
npm-metadata no-description AI (npm-metadata): Scoped monorepo package; missing description is consistent across the @notion-kit/* family. ai
phantom-deps phantom-dep:@hookform/resolvers AI (phantom-deps): Listed as a runtime dependency; phantom detection likely misses indirect usage in bundled output. ai

Versions (showing 16 of 16)

Version Deps Published
0.17.0 5 / 10
0.16.0 5 / 10
0.15.1 5 / 10
0.15.0 5 / 10
0.11.0 6 / 9
0.10.0 6 / 9
0.9.0 6 / 9
0.8.0 5 / 9
0.7.0 5 / 9
0.6.1 5 / 9
0.6.0 5 / 9
0.5.0 5 / 9
0.4.0 5 / 9
0.3.0 5 / 9
0.2.0 5 / 9
0.1.0 5 / 9

v0.3.0

1 finding
INFO No provenance attestation provenance

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

v0.2.0

1 finding
INFO No provenance attestation provenance

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

v0.1.0

1 finding
INFO No provenance attestation provenance

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