← Home

encrypted-attr

npm Repository Homepage

Encrypted model attributes in your favourite ORM.

7
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

simonratner

Keywords

attr_encryptedencryptedattributepropertymodelorm

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:base64-decode AI (semgrep): Base64 decoding is used to decode user-supplied encryption keys — standard and expected behavior for a cryptographic library. Not a malicious payload indicator. ai
publish-pattern new-deps-added AI (publish-pattern): safe-buffer is a well-established, widely-trusted Node.js Buffer polyfill. Added as a legitimate replacement for node-aes-gcm; no risk. ai

Versions (showing 7 of 7)

Version Deps Published
1.1.0 2 / 4
1.0.6 1 / 4
1.0.5 2 / 4
1.0.4 2 / 4
1.0.3 2 / 4
1.0.2 2 / 4
1.0.1 3 / 4

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

1 finding
LOW No provenance attestation provenance

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

v1.0.5

1 finding
LOW No provenance attestation provenance

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

v1.0.4

1 finding
LOW No provenance attestation provenance

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

v1.0.3

1 finding
LOW No provenance attestation provenance

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

v1.0.2

1 finding
LOW No provenance attestation provenance

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

v1.0.1

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.