@daybrush/utils MIT 24 versions

@daybrush/utils

npm Repository Homepage

utils for daybrush

24

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

Maintainers

younkue

Keywords

daybrushutilsdomcsscolorrgbahslasplitSpacesplitQuotosplitCommasplitBracketcamelizedecamelizenowrequestAnimationFramecancelAnimationFrametransformfilteranimationcrossbrowserrgbhslisUndefinedisFunctionisStringisNumberdotfindfindIndx

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	missing-githead	AI (provenance): No behavioral change; metadata-only signal for a trusted long-running package.	ai	2026/07/27
publish-pattern	dormant-publish	AI (publish-pattern): Dormancy explained by stable, mature utils package with unchanged content.	ai	2026/07/27

Versions (showing 24 of 24)

Version	Deps	Published
1.13.0	0 / 27	2023-06-04
1.12.2	0 / 27	2023-06-04
1.12.1	0 / 27	2023-05-31
1.12.0	0 / 27	2023-05-30
1.11.0	0 / 27	2023-04-02
1.10.4	0 / 27	2023-03-31
1.10.3	0 / 27	2023-03-16
1.10.2	0 / 27	2022-12-17
1.10.1	0 / 27	2022-12-15
1.10.0	0 / 27	2022-09-15
1.9.1	0 / 27	2022-08-26
1.9.0	0 / 27	2022-08-26
1.8.0	0 / 27	2022-08-25
1.7.1	0 / 27	2022-06-17
1.7.0	0 / 27	2022-06-07
1.6.0	0 / 27	2021-07-08
1.5.0	0 / 27	2021-06-20
1.4.0	0 / 27	2020-12-01
1.3.1	0 / 27	2020-11-03
1.3.0	0 / 27	2020-11-02
1.2.0	0 / 27	2020-11-01
1.1.1	0 / 27	2020-10-31
1.1.0	0 / 27	2020-10-18
1.0.0	0 / 27	2020-08-21

v1.12.2

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: younkue.

LOW No provenance attestation provenance

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

v1.12.1

1 finding

LOW No provenance attestation provenance

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

v1.12.0

1 finding

LOW No provenance attestation provenance

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

v1.11.0

1 finding

LOW No provenance attestation provenance

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

v1.10.4

1 finding

LOW No provenance attestation provenance

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

v1.10.3

1 finding

LOW No provenance attestation provenance

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

v1.10.2

1 finding

LOW No provenance attestation provenance

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

v1.10.1

1 finding

LOW No provenance attestation provenance

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

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.1

1 finding

LOW No provenance attestation provenance

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

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.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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.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.