← Home

@enterprisestandard/core

14
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

enterprisestandard

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:dist/shared/core-9dvscte3.js AI (source-diff): Minified bundle output, no malicious behavior in sample. ai
provenance missing-githead AI (provenance): Minor publish-metadata gap, not a behavioral signal; provenance direction unchanged. ai
source-diff obfuscated-file:dist/shared/core-cf4cna3e.js AI (source-diff): File is standard minified build output with readable OAuth/OIDC validation logic; not malicious obfuscation. ai
typosquat typosquat.levenshtein:cors AI (typosquat): Scoped package @enterprisestandard/core is not impersonating cors; name similarity is coincidental within a legitimate namespace. ai

Versions (showing 14 of 14)

Version Deps Published
0.0.20 1 / 0
0.0.19 0 / 0
0.0.18 0 / 0
0.0.17 0 / 0
0.0.16 0 / 0
0.0.14 0 / 0
0.0.13 0 / 0
0.0.12 0 / 0
0.0.11 0 / 0
0.0.10 0 / 0
0.0.9 0 / 0
0.0.8 0 / 0
0.0.7 0 / 0
0.0.6 0 / 0

v0.0.20

3 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: enterprisestandard.

HIGH New obfuscated file: dist/shared/core-9dvscte3.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.