← Home

unicode-properties

npm Repository Homepage

Provides fast access to unicode character properties

9
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

devongovett

Keywords

unicodemetadatacharactercodepoint

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:dist/main.cjs AI (source-diff): Parcel bundler output, not obfuscation; stable build artifact. ai
source-diff obfuscated-file:dist/module.mjs AI (source-diff): Parcel bundler output, not obfuscation; stable build artifact. ai
source-diff obfuscated-file:unicode-properties.browser.es.js AI (source-diff): Rollup-bundled browser build of unicode tables; minified not obfuscated. ai
source-diff source-size-tripled AI (source-diff): Bundled unicode data tables account for size growth. ai

Versions (showing 9 of 9)

Version Deps Published
1.4.1 2 / 3
1.4.0 2 / 3
1.3.1 2 / 8
1.3.0 2 / 8
1.2.2 2 / 8
1.2.1 2 / 8
1.2.0 2 / 8
1.1.0 2 / 3
1.0.0 2 / 3

v1.4.0

3 findings
HIGH New obfuscated file: dist/main.cjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: dist/module.mjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v1.3.1

2 findings
HIGH New obfuscated file: unicode-properties.browser.es.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v1.3.0

2 findings
HIGH New obfuscated file: unicode-properties.browser.es.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v1.2.2

2 findings
HIGH New obfuscated file: unicode-properties.browser.es.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v1.2.1

2 findings
HIGH New obfuscated file: unicode-properties.browser.es.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

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

1 finding
LOW No provenance attestation provenance

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

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.