← Home

@starasia/date

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

Maintainers

rizkyizhbayudsatriyorafli.personaldeveloper_starperkasaprawitohudoromuhfikri4

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Low-risk UI component; local publish workflow is plausible and no other risk signals present. ai
typosquat typosquat.levenshtein:vite AI (typosquat): Scoped UI component package; Levenshtein match to 'vite' is coincidental, not impersonation. ai

Versions (showing 31 of 31)

Version Deps Published
5.6.0 0 / 10
5.5.0 0 / 10
5.4.2 0 / 10
5.4.1 0 / 10
5.4.0 0 / 10
5.3.2 0 / 10
5.3.1 0 / 10
5.3.0 0 / 10
5.2.5 0 / 10
5.2.3 0 / 10
5.2.2 0 / 10
5.2.1 0 / 10
5.2.0 0 / 10
5.1.1 0 / 10
5.1.0 0 / 10
5.0.3 0 / 10
5.0.2 0 / 10
5.0.0 0 / 10
4.1.0 0 / 10
3.1.2 0 / 10
3.1.1 0 / 10
3.0.0 0 / 10
2.0.2 0 / 10
2.0.1 0 / 10
2.0.0 0 / 10
1.0.5 0 / 10
1.0.4 0 / 10
1.0.3 0 / 10
1.0.2 0 / 10
1.0.1 0 / 10
1.0.0 0 / 10

v5.6.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.

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

v5.4.2

1 finding
INFO No provenance attestation provenance

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